CVE-2026-41308: pglombardo PasswordPusher · Authentication Bypass Using an Alternate Path or Channel
Affects pglombardo PasswordPusherSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium : upgrade to 2.4.2 or 1.69.3 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.4.2, 1.69.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 8 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 30 Oct 2026.
What to do
Upgrade PasswordPusher to 2.4.2 or 1.69.3; pglombardo/PasswordPusher to 1.69.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| pglombardoPasswordPusher | Affected
| Fixed in
|
| pglombardoPasswordPusher | Affected
| Fixed in
|
GitHubpglombardo/PasswordPusherpkg:github/pglombardo/PasswordPusherOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in PasswordPusher versions 1.69.3 and 2.4.2. Users should upgrade to these or later versions to remediate the vulnerability. No vendor advisory was provided to indicate alternative mitigations or that no action is required.
Description
Password Pusher is an open source application to communicate sensitive information over the web. Prior to versions 1.69.3 and 2.4.2, a security issue in OSS PasswordPusher allowed unauthenticated creation of file-type pushes through a generic JSON API create path under certain configurations. This could bypass the intended authentication boundary for file push creation. This issue has been patched in versions 1.69.3 and 2.4.2.