CVE-2026-47891

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 3 sources updated this week
9.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.8Exploit: None knownExposed services: Not assessed

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

The CVE record's CNA (VMware by Broadcom) lists Spring Framework versions 7.0.0 up to and including 7.0.8, 6.2.0 up to and including 6.2.19, 6.1.0 up to and including 6.1.28, 6.0.0 up to and including 6.0.30 and 2 more ranges as affected. No release containing a fix is confirmed on record.

A Spring WebFlux application that relies on the Aalto XML processor to parse XML input does not correctly enforce the maxInMemorySize limit. Spring Framework 7.0.0 - 7.0.8 Spring Framework 6.2.0 - 6.2.19 Spring Framework 6.1.0 - 6.1.28 Spring Framework 6.0.0 - 6.0.30 Spring Framework 5.3.0 - 5.3.49 Spring Framework 5.2.25.RELEASE and earlier

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/100

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 (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation0.5% × 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 total (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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.5%
EPSS %ILE
42nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (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 27, 2026

Last Modified

September 2, 2026

Advisory Details (1)

Auto-updated Oct 8, 2026
No fix on record yet.
Web page

Spring Framework maxInMemorySize Bypassed in Jaxb2Decoder

https://spring.io/security/cve-2026-47891

Vendor Advisories for CVE-2026-47891(1)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libspring-java4.3.30-2, 4.3.30-3, 4.3.30-4
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libspring-java4.3.30-3, 4.3.30-4
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libspring-java4.3.30-3, 4.3.30-4
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 26× in last 7d / 172× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 100 of 305 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 205 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 09:16 UTCEG score recompute
  2. 2026-10-14 09:16 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  4. 2026-10-13 06:29 UTCEG score recompute
  5. 2026-10-13 06:28 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  7. 2026-10-12 16:01 UTCEG score recompute
  8. 2026-10-12 07:27 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-11 19:44 UTCEG score recompute
  10. 2026-10-11 16:58 UTCEG score recompute
  11. 2026-10-11 14:23 UTCEG score recompute
  12. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  13. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  14. 2026-10-10 14:11 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-10-10 09:50 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-10 05:24 UTCEG score recompute
  17. 2026-10-10 05:24 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  19. 2026-10-09 07:41 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-09 03:12 UTCEG score recompute
  21. 2026-10-09 03:12 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  23. 2026-10-08 05:50 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-08 01:24 UTCEG score recompute
  25. 2026-10-08 01:24 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
Show 75 more
  1. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  2. 2026-10-07 10:13 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-07 05:52 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-10-07 01:31 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-10-06 21:10 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-06 16:31 UTCEG score recompute
  7. 2026-10-06 16:31 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  9. 2026-10-06 11:55 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-10-06 07:34 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-10-06 00:56 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-10-05 18:55 UTCEG score recompute
  13. 2026-10-05 18:55 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  15. 2026-10-05 14:31 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-05 10:05 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-10-05 05:44 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-05 01:23 UTCEG score recompute
  19. 2026-10-05 01:23 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  21. 2026-10-04 20:34 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-04 15:34 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-04 10:58 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-04 06:16 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-10-04 01:55 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  26. 2026-10-03 20:23 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  27. 2026-10-03 16:03 UTCEG score recompute
  28. 2026-10-03 16:03 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  29. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  30. 2026-10-03 04:52 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  31. 2026-10-03 00:29 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  32. 2026-10-02 19:57 UTCEG score recompute
  33. 2026-10-02 19:57 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  34. 2026-10-02 15:36 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  35. 2026-10-02 11:00 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  36. 2026-10-02 06:20 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  37. 2026-10-02 01:14 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  38. 2026-10-01 19:54 UTCEG score recompute
  39. 2026-10-01 19:54 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  40. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  41. 2026-10-01 14:14 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  42. 2026-10-01 09:52 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  43. 2026-10-01 05:32 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  44. 2026-10-01 01:01 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  45. 2026-09-30 19:56 UTCEG score recompute
  46. 2026-09-30 19:56 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  47. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  48. 2026-09-30 09:36 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  49. 2026-09-30 05:09 UTCEG score recompute
  50. 2026-09-30 05:09 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  51. 2026-09-29 12:20 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  52. 2026-09-29 06:00 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  53. 2026-09-29 01:39 UTCEG score recompute
  54. 2026-09-29 01:39 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  55. 2026-09-28 21:19 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  56. 2026-09-28 15:48 UTCEG score recompute
  57. 2026-09-28 15:48 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  58. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  59. 2026-09-28 11:24 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  60. 2026-09-28 07:03 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  61. 2026-09-28 02:37 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  62. 2026-09-27 22:10 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  63. 2026-09-27 17:27 UTCEG score recompute
  64. 2026-09-27 17:27 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  65. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  66. 2026-09-27 13:05 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  67. 2026-09-27 08:43 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  68. 2026-09-27 04:22 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  69. 2026-09-27 00:00 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  70. 2026-09-26 19:24 UTCEG score recompute
  71. 2026-09-26 19:24 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  72. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  73. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  74. 2026-09-25 13:16 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8
  75. 2026-09-25 08:55 UTCGHSA enrichmentGHSA-7p67-m4j8-h4vx · GitHub severity CRITICAL · GitHub CVSS 9.8

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-47891?
CVE-2026-47891 is a critical-severity vulnerability; its CVE record was published on August 27, 2026. A Spring WebFlux application that relies on the Aalto XML processor to parse XML input does not correctly enforce the maxInMemorySize limit. Spring Framework 7.0.0 - 7.0.8 Spring Framework 6.2.0 - 6.2.19 Spring Framework 6.1.0 - 6.1.28 Spring Framework 6.0.0 - 6.0.30 Spring Framework 5.3.0 - 5.3.49…
When was the CVE record for CVE-2026-47891 published?
The CVE record for CVE-2026-47891 was published on August 27, 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 2, 2026; the record at its source may have been updated since.
Is CVE-2026-47891 actively exploited?
CVE-2026-47891 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-47891?
CVE-2026-47891 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-47891?
No fix for CVE-2026-47891 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (VMware by Broadcom) lists Spring Framework versions 7.0.0 up to and including 7.0.8, 6.2.0 up to and including 6.2.19, 6.1.0 up to and including 6.1.28, 6.0.0 up to and including 6.0.30 and 2 more ranges as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-47891 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-47891

Explore →

Is Your Infrastructure Affected by CVE-2026-47891?

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

Book a Demo →Browse All CVEs