# CVE-2026-61458: PasswordPusher < 2.9.2 Passphrase Brute-Force via Unthrottled Endpoint

> Attackers can brute-force PasswordPusher passphrases via an unthrottled endpoint, potentially recovering secrets if tokens are known.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jul 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-59w3-h5v2-c4xw, GHSA-w4jg-w96x-q3wh

## What is CVE-2026-61458?

CVE-2026-61458 is a high-severity vulnerability in pglombardo PasswordPusher, published on 13 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PasswordPusher before 2.9.2 contains a brute-force vulnerability in the POST /p/:token/access endpoint that lacks route-specific rate limiting and per-push lockout mechanisms. Attackers who know a push token can systematically guess passphrases at 120 attempts per minute without triggering any push-level defense, making short or dictionary-derived passphrases practically recoverable within hours or days.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

## Which versions are affected by CVE-2026-61458?


## How do I fix CVE-2026-61458?

No fix has been published for CVE-2026-61458 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-61458 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61458 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-61458 and fix it if it is affected.

What it is: CVE-2026-61458 is a high-severity vulnerability in pglombardo PasswordPusher, published on 13 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61458 exists.

Affected product: pglombardo PasswordPusher. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-61458/ (Markdown: https://insights.sbomify.com/CVE-2026-61458/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-61458
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-61458
- OSV: https://osv.dev/vulnerability/CVE-2026-61458

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-61458/
Summaries are generated and may contain mistakes; the official description above is the record.