CVE-2013-4152: The Spring OXM wrapper in Spring Framework before 3.2.4 and 4.0.0.M1, when using the JAXB marshaller, does not

Q: How do I fix CVE-2013-4152?

spring framework: downgrade or apply the listed mitigation; spring framework: upgrade to newer than 3.2.3. Exact commands for each OS are on this page.

Q: Is CVE-2013-4152 being exploited?

CVE-2013-4152 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2013-4152 affect?

CVE-2013-4152 affects spring framework, spring framework. Severity is medium (CVSS 6.8). The Spring OXM wrapper in Spring Framework before 3.2.4 and 4.0.0.M1, when using the JAXB marshaller, does not disable entity resolution, which allows context-dependent attackers to read arbitrary files, cause a denial of service, and condu

Q: How urgent is CVE-2013-4152?

Priority 53/100. EPSS top 2%: very likely to be exploited; Public exploit reference

This week

MEDIUM 6.8DOWNGRADEUPGRADE

CVE-2013-4152 is a medium-severity flaw (CVSS 6.8) affecting spring framework, spring framework. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Spring OXM wrapper in Spring Framework before 3.2.4 and 4.0.0.M1, when using the JAXB marshaller, does not disable entity resolution, which allows context-dependent attackers to read arbitrary files, cause a denial of service, and conduct CSRF attacks via an XML external entity declaration in conjunction with an entity reference in a (1) DOMSource, (2) StAXSource, (3) SAXSource, or (4) StreamSource, aka an XML External Entity (XXE) issue.

Why this priority

EPSS top 2%: very likely to be exploited
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	6.8 (Medium)
EPSS exploit chance	25.6% (top 2%)
CISA exploited list	No
Weakness	CWE-264
Published	2014-01-23
Last modified	2026-06-16

Publisher (CNA): Red Hat, Inc. · Vendor: springsource · vmware

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2014-01-23 21:55 UTCPublished CVE record published
2026-06-16 23:56 UTCUpdated Record last modified

springsource spring framework DOWNGRADE

Affected: 3.0.0 · 3.0.0 m1 · 3.0.0 m2 · 3.0.0 m3 · 3.0.0 m4 · 3.0.0 rc1 · 3.0.0 rc2 · 3.0.0 rc3

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.0.0

1. Check installed version

apt-cache policy spring-framework || rpm -q spring-framework || spring-framework --version

2. No fixed release: DOWNGRADE to a release before 3.0.0 (Debian / Ubuntu)

apt-cache madison spring-framework sudo apt install spring-framework=<VERSION_BEFORE_3.0.0> sudo apt-mark hold spring-framework

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list spring-framework sudo dnf downgrade spring-framework-<VERSION_BEFORE_3.0.0> sudo dnf versionlock add spring-framework

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

vmware spring framework UPGRADE

Affected: <= 3.2.3 · 3.0.6 · 3.0.7 · 3.1.0 · 3.1.1 · 3.1.2 · 3.1.3 · 3.1.4

Fixed in: newer than 3.2.3

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy spring-framework || rpm -q spring-framework || spring-framework --version

2. UPGRADE to newer than 3.2.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade spring-framework

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade spring-framework

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2013-4152?

spring framework: downgrade or apply the listed mitigation; spring framework: upgrade to newer than 3.2.3. Exact commands for each OS are on this page.

Is CVE-2013-4152 being exploited?

CVE-2013-4152 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2013-4152 affect?

CVE-2013-4152 affects spring framework, spring framework. Severity is medium (CVSS 6.8). The Spring OXM wrapper in Spring Framework before 3.2.4 and 4.0.0.M1, when using the JAXB marshaller, does not disable entity resolution, which allows context-dependent attackers to read arbitrary files, cause a denial of service, and condu

How urgent is CVE-2013-4152?

Priority 53/100. EPSS top 2%: very likely to be exploited; Public exploit reference

Software pages

Spring Framework vulnerabilities · VMware vulnerabilities

Related CVEs

CVE-2026-22740 MEDIUM 6.5 UPGRADE A WebFlux server application that processes multipart requests creates temp files for parts larger than 10 K
CVE-2026-22745 MEDIUM 5.3 UPGRADE Spring MVC and WebFlux applications are vulnerable to Denial of Service attacks when resolving static resource
CVE-2026-22741 LOW 3.1 UPGRADE Spring MVC and WebFlux applications are vulnerable to cache poisoning when resolving static resources. More
CVE-2022-22971 MEDIUM 6.5 UPGRADE DOWNGRADE In spring framework versions prior to 5.3.20+ , 5.2.22+ and old unsupported versions, application with a STOMP
CVE-2020-5398 HIGH 7.5 UPGRADE DOWNGRADE In Spring Framework, versions 5.2.x prior to 5.2.3, versions 5.1.x prior to 5.1.13, and versions 5.0.x prior t

References

← Back to latest CVEs