Skip to main content
VulnerabilityPublished Updated

CVE-2026-62382: pglombardo PasswordPusher · Incorrect Authorization

Affects pglombardo PasswordPusherSource CVE Database V5

0
Compare

Not known to be exploited · public detection template (Nuclei) · CVSS 6.9 Medium : upgrade to 2.9.6 when convenient.

Data as of 20 Nov 2026, 17:35 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.1% chance of exploitation in 30 days – higher than 68% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.9.6
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Aug 2026

  2. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade PasswordPusher and passwordpusher to 2.9.6.

Affected software

ProductAffectedFixed in
pglombardoPasswordPusherAffected
  • <2.9.6
Fixed in
  • 2.9.6
RubyGemspasswordpusherpkg:gem/passwordpusherOther threatsAffected
  • >=1.45.11 <2.9.6
Fixed in
  • 2.9.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade PasswordPusher to version 2.9.6 or later, where this authorization vulnerability is fixed. Until then, consider disabling anonymous pushes if possible to mitigate risk. Patch status is not explicitly stated as 'official-fix' or 'patchAvailable' but the issue is fixed in version 2.9.6 according to the description.

Description

PasswordPusher versions 1.45.11 through 2.9.5 have an improper authorization vulnerability in the push deletion logic. The vulnerability allows an attacker who knows the secret URL of an anonymously created push to delete it permanently, bypassing restrictions set by the creator. This occurs because the ownership check incorrectly treats nil values as equal, enabling deletion without authentication or passphrase. The issue affects deployments that allow anonymous pushes, which is the default configuration. The vulnerability is fixed in version 2.9.6.

References

Community reviews

Loading reviews…