Skip to content
Web

CVE-2026-61458

8.7
High
EPSS 0.41%Patch availableJul 14, 2026

Brute-force allows recovery of PasswordPusher push passphrases.

common questions

Is CVE-2026-61458 being exploited?

Not confirmed. CVE-2026-61458 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.41% probability of exploitation in the next 30 days.

How severe is CVE-2026-61458?

CVE-2026-61458 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-61458?

Yes. A fix has been recorded for CVE-2026-61458. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-61458 affect?

CVE-2026-61458 affects PasswordPusher < 2.9.2 (self-hosted), Instances exposing POST /p/:token/access, Short or dictionary-derived push passphrases. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-61458?

Upgrade to PasswordPusher 2.9.2; enforce strong passphrases and add rate limiting.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
PasswordPusher < 2.9.2 (self-hosted)Instances exposing POST /p/:token/accessShort or dictionary-derived push passphrases
impact

Remote brute-force of push passphrases (≈120 attempts/min) enabling disclosure of shared secrets/credentials.

action required

Immediate action required

affected versions
pglombardo PasswordPusher
  • affected< 2.9.2
vendor says fixed in2.9.2

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free