# CVE-2026-87816: PasswordPusher before 2.11.1 Race Condition View Limit Bypass

> Unauthenticated attackers can bypass view limits via race conditions to access one-time secrets multiple times in PasswordPusher.

- **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:** 9 Sep 2026
- **Updated:** 9 Sep 2026
- **Also known as:** GHSA-6q3c-57pp-wvpp, GHSA-j5vw-cw8p-7f7g

## What is CVE-2026-87816?

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

### Official description

PasswordPusher before 2.11.1 contains a time-of-check-to-time-of-use race condition in view limit enforcement that allows unauthenticated attackers to bypass expire_after_views limits. Attackers can send concurrent requests to the show endpoint to access one-time secrets multiple times before the view count is incremented and the push expires.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

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


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

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

## Is CVE-2026-87816 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-87816 is a high-severity vulnerability in pglombardo PasswordPusher, published on 9 Sep 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-87816 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-87816/ (Markdown: https://insights.sbomify.com/CVE-2026-87816/index.md)
```

## Sources

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

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