CVE-2026-54225

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-06. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

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

Apache CXF allows to control the maximum attachment size via the "attachment-max-size". Prior to Apache CXF 4.2.3 and 4.1.8 and 3.6.12, there was no default placed on this size, meaning that a denial of service attack is possible if the user doesn't explicitly set the limit. Users should update to Apache CXF 4.2.3 or 4.1.8 or 3.6.12 which fixes this problem by imposing a default attachment size limit of 50mb.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
39%
KEV
Not listed

Published

August 6, 2026

Last Modified

August 7, 2026

Advisory Details (1)

Auto-updated Aug 6, 2026
No patch confirmed yet.
generic
https://lists.apache.org/thread/h2bjqm6g58z0j6893qzh728kdtk1byfy

Vendor Advisories for CVE-2026-54225(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 29× in last 7d / 73× 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-21 01:10 UTCEG score recompute
  2. 2026-08-21 01:10 UTCGHSA enrichment
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 14:19 UTCGHSA enrichment
  5. 2026-08-20 03:23 UTCEG score recompute
  6. 2026-08-20 03:23 UTCGHSA enrichment
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 16:19 UTCGHSA enrichment
  9. 2026-08-19 05:27 UTCGHSA enrichment
  10. 2026-08-18 18:36 UTCEG score recompute
  11. 2026-08-18 18:36 UTCGHSA enrichment
  12. 2026-08-18 13:48 UTCEPSS rescore
  13. 2026-08-18 07:45 UTCGHSA enrichment
  14. 2026-08-17 20:50 UTCEG score recompute
  15. 2026-08-17 20:50 UTCGHSA enrichment
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 09:58 UTCGHSA enrichment
  18. 2026-08-16 23:08 UTCEG score recompute
  19. 2026-08-16 23:08 UTCGHSA enrichment
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 12:16 UTCEG score recompute
  22. 2026-08-16 12:16 UTCGHSA enrichment
  23. 2026-08-16 02:14 UTCEPSS rescore
  24. 2026-08-16 01:26 UTCGHSA enrichment
  25. 2026-08-15 14:35 UTCGHSA enrichment
Show 48 more
  1. 2026-08-15 03:44 UTCEG score recompute
  2. 2026-08-15 03:44 UTCGHSA enrichment
  3. 2026-08-15 01:30 UTCEPSS rescore
  4. 2026-08-14 16:52 UTCGHSA enrichment
  5. 2026-08-14 05:58 UTCEG score recompute
  6. 2026-08-14 05:58 UTCGHSA enrichment
  7. 2026-08-13 22:00 UTCEPSS rescore
  8. 2026-08-13 19:07 UTCGHSA enrichment
  9. 2026-08-13 08:16 UTCGHSA enrichment
  10. 2026-08-12 21:25 UTCEG score recompute
  11. 2026-08-12 21:25 UTCGHSA enrichment
  12. 2026-08-12 13:51 UTCEPSS rescore
  13. 2026-08-12 10:34 UTCGHSA enrichment
  14. 2026-08-11 23:42 UTCEG score recompute
  15. 2026-08-11 23:42 UTCGHSA enrichment
  16. 2026-08-11 12:51 UTCGHSA enrichment
  17. 2026-08-11 02:00 UTCEG score recompute
  18. 2026-08-11 02:00 UTCGHSA enrichment
  19. 2026-08-11 00:00 UTCEPSS rescore
  20. 2026-08-10 15:09 UTCGHSA enrichment
  21. 2026-08-10 04:17 UTCGHSA enrichment
  22. 2026-08-09 17:26 UTCEG score recompute
  23. 2026-08-09 17:26 UTCGHSA enrichment
  24. 2026-08-09 13:46 UTCEPSS rescore
  25. 2026-08-09 06:35 UTCGHSA enrichment
  26. 2026-08-08 19:44 UTCEG score recompute
  27. 2026-08-08 19:44 UTCGHSA enrichment
  28. 2026-08-08 16:37 UTCEPSS rescore
  29. 2026-08-08 08:52 UTCGHSA enrichment
  30. 2026-08-07 22:01 UTCEG score recompute
  31. 2026-08-07 22:01 UTCGHSA enrichment
  32. 2026-08-07 11:10 UTCGHSA enrichment
  33. 2026-08-07 00:19 UTCGHSA enrichment
  34. 2026-08-07 00:16 UTCGHSA enrichment
  35. 2026-08-06 18:42 UTCEG score recompute
  36. 2026-08-06 18:42 UTCGHSA enrichment
  37. 2026-08-06 16:31 UTCEG score recompute▲ 7.50
  38. 2026-08-06 16:31 UTCGHSA enrichment
  39. 2026-08-06 16:30 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  40. 2026-08-06 16:06 UTCEG score recompute▼ 7.50
  41. 2026-08-06 16:06 UTCGHSA enrichment
  42. 2026-08-06 16:05 UTCNVD update
  43. 2026-08-06 15:31 UTCEG score recompute▲ 7.50
  44. 2026-08-06 15:31 UTCGHSA enrichment
  45. 2026-08-06 15:31 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  46. 2026-08-06 11:22 UTCNVD update
  47. 2026-08-06 11:04 UTCEG score recompute
  48. 2026-08-06 11:03 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54225?
CVE-2026-54225 is a high vulnerability published on August 6, 2026. Apache CXF allows to control the maximum attachment size via the "attachment-max-size". Prior to Apache CXF 4.2.3 and 4.1.8 and 3.6.12, there was no default placed on this size, meaning that a denial of service attack is possible if the user doesn't explicitly set the limit. Users should update to…
When was CVE-2026-54225 disclosed?
CVE-2026-54225 was first published in the National Vulnerability Database on August 6, 2026, with the most recent update on August 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54225 actively exploited?
CVE-2026-54225 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 61.2% of all scored CVEs.
What is the CVSS score of CVE-2026-54225?
CVE-2026-54225 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-54225?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54225, 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

Explore the affected products and dependency analysis for CVE-2026-54225

Explore →

Is Your Infrastructure Affected by CVE-2026-54225?

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

Start Free Scan →Browse All CVEs