CVE-2026-54625

MEDIUMPre-NVD 4.84.8
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 96% of all CVEs by exploit prediction. 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
4.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

django CMS is a content management system powered by Django. Prior to 5.0.8 and in 5.1.0a1, the django CMS page cache in cms/cache/page.py ignores request headers declared by plugins through get_vary_cache_on(). The _page_cache_key function includes the cache prefix, site, language, path, and timezone but not the declared header values. Although set_page_cache adds those names to the response Vary header, get_page_cache retrieves the first stored variant under the same header-agnostic key. When CMS_PAGE_CACHE is enabled and a plugin varies content on a header such as Country-Code, one visitor can receive another visitor’s request-specific content, and an unauthenticated attacker can prime the cache with attacker-chosen content. This issue is fixed in versions 5.0.8 and 5.1.0.

CVSS v3
4.8
EG Score
4.8(medium)
EG Risk
22(Track)
EG Risk 22/100SSVC: Track

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 computed
Severity48% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

August 20, 2026

Last Modified

August 20, 2026

Advisory Details (7)

Auto-updated Aug 20, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available

Page cache ignores plugin-declared Vary headers (disclosure & poisoning) · Advisory · django-cms/django-cms · GitHub

Affected: 5.0.8: the page cache now folds the request's values implements

https://github.com/django-cms/django-cms/security/advisories/GHSA-fwjf-m4qw-9f2x
github_release Patch Available

5.1.0

Patch available: django-cms/django-cms 5.1.0

https://github.com/django-cms/django-cms/releases/tag/5.1.0
github_release Patch Available

5.0.8

Patch available: django-cms/django-cms 5.0.8

https://github.com/django-cms/django-cms/releases/tag/5.0.8
github_pr Patch Available

fix: Honour plugin-declared Vary headers in the page cache key (#8646)

Patch available: django-cms/django-cms 5.0.8 (PR #8647 merged 2026-06-05)

https://github.com/django-cms/django-cms/pull/8647
github_pr Patch Available

fix: Honour plugin-declared Vary headers in the page cache key

Patch available: django-cms/django-cms 5.1.0 (PR #8646 merged 2026-06-08)

https://github.com/django-cms/django-cms/pull/8646
github_commit Patch Available

commit d5dc1efa18d1 (django-cms/django-cms)

Patch available: django-cms/django-cms 5.0.8 (contains commit d5dc1efa18d1)

https://github.com/django-cms/django-cms/commit/d5dc1efa18d157445491c4b12c2dd1efd56f439f
github_commit Patch Available

commit 8758714b865f (django-cms/django-cms)

Patch available: django-cms/django-cms 5.1.0 (contains commit 8758714b865f)

https://github.com/django-cms/django-cms/commit/8758714b865ffa79c6bcd0e5c503958ea48885aa

Vendor Advisories for CVE-2026-54625(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)
PackageVulnerable rangeFixed inDependents
django-cms2.0.1 ... 5.0.7 (140 versions)5.0.8

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 12× 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.

  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-25 12:23 UTCEG score recompute
  3. 2026-08-24 13:55 UTCEG score recompute
  4. 2026-08-23 15:32 UTCEG score recompute
  5. 2026-08-23 00:19 UTCEPSS rescore
  6. 2026-08-22 17:08 UTCEG score recompute
  7. 2026-08-21 23:49 UTCEPSS rescore
  8. 2026-08-20 20:20 UTCEG score recompute
  9. 2026-08-20 19:52 UTCEG score recompute
  10. 2026-08-20 18:17 UTCEG score recompute
  11. 2026-08-20 18:07 UTCEG score recompute
  12. 2026-08-20 18:06 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-54625?
CVE-2026-54625 is a medium vulnerability published on August 20, 2026. django CMS is a content management system powered by Django. Prior to 5.0.8 and in 5.1.0a1, the django CMS page cache in cms/cache/page.py ignores request headers declared by plugins through getvarycacheon(). The pagecachekey function includes the cache prefix, site, language, path, and timezone…
When was CVE-2026-54625 disclosed?
CVE-2026-54625 was first published in the National Vulnerability Database on August 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54625 actively exploited?
CVE-2026-54625 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 95.8% of all scored CVEs.
What is the CVSS score of CVE-2026-54625?
CVE-2026-54625 has a CVSS v3 base score of 4.8 (NVD).
How do I remediate CVE-2026-54625?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54625, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-54625?

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