CVE-2026-54723

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 6.5 from GitHub Security Advisory (severity: MODERATE) published 2026-08-18. A secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-77701 (ENISA EUVD) · GHSA-m5pq-69xg-vcq3 (GitHub Security Advisories) · PYSEC-2026-3661 (OSV.dev)Source: ENISA EUVD

6.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
44
EG Risk 44/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
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
38th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 18, 2026

Last Modified

September 30, 2026

Advisory Details (2)

Auto-updated Sep 14, 2026
Patch available. Sources: github, github_commit.
GitHub commit

commit b4ea49fed4a6 (devpi/devpi)

Fix landed in devpi/devpi commit b4ea49fed4a6 — awaiting tagged release

https://github.com/devpi/devpi/commit/b4ea49fed4a6233d63f8509c3bf7efafc9b2db17
GitHub advisoryMentions a patch (unverified)

Database contents leak · Advisory · devpi/devpi · GitHub

https://github.com/devpi/devpi/security/advisories/GHSA-m5pq-69xg-vcq3

Vendor 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.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipdevpi-server @ 6.20.2 (fixes < 6.20.2)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
devpi-server0.7 ... 6.9.2 (107 versions)
  • every version up to 6.20.2: fixed in 6.20.2
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 32× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 16:53 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  2. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  3. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  4. 2026-11-10 16:44 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  5. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  6. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  7. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  8. 2026-11-06 16:38 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  9. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  10. 2026-11-04 16:35 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  11. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  12. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  13. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  14. 2026-11-01 07:44 UTCGHSA enrichmentGHSA-m5pq-69xg-vcq3 · GitHub severity MODERATE · GitHub CVSS 6.5
  15. 2026-11-01 07:44 UTCEchelonGraph re-scored
  16. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  17. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  18. 2026-10-30 11:25 UTCOSV refresh
  19. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  20. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  21. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  22. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  23. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  24. 2026-10-25 14:19 UTCEchelonGraph re-scored
  25. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
Show 63 more
  1. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  2. 2026-10-22 21:19 UTCEchelonGraph re-scored
  3. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  4. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  5. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  6. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  7. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  8. 2026-10-18 03:30 UTCEchelonGraph re-scored
  9. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  10. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  11. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  12. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  13. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  14. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  15. 2026-10-12 15:56 UTCEchelonGraph re-scored
  16. 2026-10-11 19:39 UTCEchelonGraph re-scored
  17. 2026-10-11 16:54 UTCEchelonGraph re-scored
  18. 2026-10-11 14:17 UTCEchelonGraph re-scored
  19. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  20. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  21. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  22. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  23. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  24. 2026-10-07 11:10 UTCEchelonGraph re-scored
  25. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  26. 2026-10-06 08:20 UTCEchelonGraph re-scored
  27. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  28. 2026-10-05 06:04 UTCEchelonGraph re-scored
  29. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  30. 2026-10-04 04:08 UTCEchelonGraph re-scored
  31. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  32. 2026-10-03 02:44 UTCEchelonGraph re-scored
  33. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  34. 2026-10-02 01:25 UTCEchelonGraph re-scored
  35. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  36. 2026-09-30 20:04 UTCEchelonGraph re-scored
  37. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  38. 2026-09-30 09:46 UTCEchelonGraph re-scored
  39. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  40. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  41. 2026-09-28 09:13 UTCEchelonGraph re-scored
  42. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  43. 2026-09-27 07:54 UTCEchelonGraph re-scored
  44. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  45. 2026-09-25 11:50 UTCEchelonGraph re-scored
  46. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  47. 2026-09-24 10:00 UTCEchelonGraph re-scored
  48. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  49. 2026-09-23 08:40 UTCEchelonGraph re-scored
  50. 2026-09-22 07:21 UTCEchelonGraph re-scored
  51. 2026-09-21 06:02 UTCEchelonGraph re-scored
  52. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  53. 2026-09-20 03:04 UTCEchelonGraph re-scored
  54. 2026-09-19 01:44 UTCEchelonGraph re-scored
  55. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  56. 2026-09-18 00:18 UTCEchelonGraph re-scored
  57. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  58. 2026-09-16 22:58 UTCEchelonGraph re-scored
  59. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  60. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  61. 2026-09-14 19:23 UTCEchelonGraph re-scored
  62. 2026-09-14 18:35 UTCEchelonGraph re-scored
  63. 2026-08-18 20:42 UTCEchelonGraph re-scoredFirst assessed: 6.5 MEDIUM

Frequently asked(5)

What is CVE-2026-54723?
CVE-2026-54723 is a medium-severity vulnerability; its CVE record was published on August 18, 2026. 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…
When was the CVE record for CVE-2026-54723 published?
The CVE record for CVE-2026-54723 was published on August 18, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-54723 actively exploited?
CVE-2026-54723 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54723?
CVE-2026-54723 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54723?
A fix for CVE-2026-54723 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54723 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54723

Explore →

Is Your Infrastructure Affected by CVE-2026-54723?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.