# CVE-2026-54723: devpi: Database contents leak

> Unauthenticated attackers can access the changelog route on primary devpi servers, leaking database contents including password hashes and causing resource exhaustion.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-m5pq-69xg-vcq3, PYSEC-2026-3661

## What is CVE-2026-54723?

CVE-2026-54723 is a medium-severity missing authorization vulnerability in devpi, published on 14 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

devpi is a Python package index staging server and packaging, testing, and release tool. Prior to 6.20.2 and 7.0.0b3, a server configured with the primary or deprecated master role allows an unauthenticated, modified GET request to the +changelog route because verify_primary does not reject a missing identity and therefore fails to require ReplicaIdentity. The response can disclose complete database content, including Argon2 password hashes and identifiers and salts for devpi-tokens; exposed hashes may be subject to dictionary attacks, and public tokens may assist attempts to derive the server secret. Large responses can also consume significant CPU, input/output capacity, and bandwidth. Servers using the standalone role are not exposed through replication, and an instance served exclusively through nginx with devpi-lockdown redirects the request to login with no known exploit. This issue is fixed in devpi-server versions 6.20.2 and 7.0.0b3.

Weakness: CWE-304 (Missing Critical Step in Authentication)

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

3 open source packages ship an affected version, including devpi-server.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `devpi-server` | PyPI | All versions | 6.20.2 |
| `devpi-server` | PyPI | All versions | 6.20.2 |
| `devpi-server` | PyPI | All versions | 6.20.2 |

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

Upgrade devpi-server to 6.20.2 or later.

## Is CVE-2026-54723 being exploited?

There is no known exploitation of CVE-2026-54723 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54723 is a medium-severity missing authorization vulnerability in devpi, published on 14 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54723 in the wild and no public exploit code.

Affected packages and fixed versions:
- devpi-server (PyPI): affected all versions; fixed in 6.20.2
- devpi-server (PyPI): affected all versions; fixed in 6.20.2
- devpi-server (PyPI): affected all versions; fixed in 6.20.2

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-54723/ (Markdown: https://insights.sbomify.com/CVE-2026-54723/index.md)
```

## Sources

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

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