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.
CVE-2026-54723
This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (35th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 6.5
- EG Score
- 6.5MEDIUMmedium confidence
- EG Risk
- 44EG Risk 44/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity65% × 45%Exploitation0% × 40%Automatability100% × 15%CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.4%
- EPSS %ILE
- 35th
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
August 18, 2026
Last Modified
September 30, 2026
Advisory Details (2)
Auto-updated Sep 14, 2026commit b4ea49fed4a6 (devpi/devpi)
Fix landed in devpi/devpi commit b4ea49fed4a6 — awaiting tagged release
https://github.com/devpi/devpi/commit/b4ea49fed4a6233d63f8509c3bf7efafc9b2db17Database contents leak · Advisory · devpi/devpi · GitHub
https://github.com/devpi/devpi/security/advisories/GHSA-m5pq-69xg-vcq3Vendor Advisories for CVE-2026-54723(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| devpi-server | 0.7 ... 6.9.2 (107 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 35× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-05 06:04 UTCEG score recompute
- 2026-10-04 23:22 UTCEPSS rescore
- 2026-10-04 04:08 UTCEG score recompute
- 2026-10-03 14:26 UTCEPSS rescore
- 2026-10-03 02:44 UTCEG score recompute
- 2026-10-02 17:56 UTCEPSS rescore
- 2026-10-02 01:25 UTCEG score recompute
- 2026-10-01 19:50 UTCEPSS rescore
- 2026-09-30 20:04 UTCEG score recompute
- 2026-09-30 15:03 UTCEPSS rescore
- 2026-09-30 09:46 UTCEG score recompute
- 2026-09-29 15:22 UTCEPSS rescore
- 2026-09-28 13:51 UTCEPSS rescore
- 2026-09-28 09:13 UTCEG score recompute
- 2026-09-27 13:48 UTCEPSS rescore
- 2026-09-27 07:54 UTCEG score recompute
- 2026-09-26 15:59 UTCEPSS rescore
- 2026-09-25 11:50 UTCEG score recompute
- 2026-09-24 14:04 UTCEPSS rescore
- 2026-09-24 10:00 UTCEG score recompute
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-23 08:40 UTCEG score recompute
- 2026-09-22 07:21 UTCEG score recompute
- 2026-09-21 06:02 UTCEG score recompute
- 2026-09-20 20:16 UTCEPSS rescore
Show 11 moreShow fewer
- 2026-09-20 03:04 UTCEG score recompute
- 2026-09-19 01:44 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 00:18 UTCEG score recompute
- 2026-09-17 19:31 UTCEPSS rescore
- 2026-09-16 22:58 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-14 19:23 UTCEG score recompute
- 2026-09-14 18:35 UTCEG score recompute
- 2026-08-18 20:42 UTCEG score recompute
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-54723?
When was CVE-2026-54723 disclosed?
Is CVE-2026-54723 actively exploited?
What is the CVSS score of CVE-2026-54723?
How do I remediate CVE-2026-54723?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54723
Is Your Infrastructure Affected by CVE-2026-54723?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.