Skip to main content
Mallory
UnratedVulnerability

CVE-2026-59393: Memory Limit Bypass in Spring Framework WebFlux XML Decoding

Updated 1 day ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-59393CWE-770

CVE-2026-59393 is a memory consumption limit bypass in Spring Framework's WebFlux XML decoding with Jaxb2Decoder when using the Aalto XML parser. A specially crafted XML request or response body can cause decoding to exceed the configured maxInMemorySize limit, potentially resulting in denial of service. This vulnerability is a follow-up to CVE-2026-47891.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Processing specially crafted XML can consume memory beyond the application's configured maxInMemorySize limit, potentially exhausting available memory and causing denial of service.

Mitigation

If you can’t patch tonight, do this now.

No separate temporary workaround is specified. Upgrade to a corresponding fixed release; no additional mitigation steps are required after upgrading.

Remediation

Patch, then assume compromise.

Upgrade Spring Framework to the corresponding fixed release: 7.0.11 (OSS), or 7.0.10.1, 6.2.21, 6.1.30, 6.0.33, 5.3.51, or 5.2.27.RELEASE (Enterprise Support Only).

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-59393 exploited in the wild?
As of Nov 20, 2026, Mallory has no reports of CVE-2026-59393 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-59393?
As of Nov 20, 2026, Mallory has found no public exploit for CVE-2026-59393.
Is there a patch for CVE-2026-59393?
Upgrade Spring Framework to the corresponding fixed release: 7.0.11 (OSS), or 7.0.10.1, 6.2.21, 6.1.30, 6.0.33, 5.3.51, or 5.2.27.RELEASE (Enterprise Support Only).
Activity feed

Recent activity

1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.