CVE-2013-6429

NONECVSS 0.0Elevated
0.0
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 90%
CISA-KEV: Not listedEPSS: 90%CVSS: —Exploit: NoneExposed: 0

A fix is available — apply it.

The SourceHttpMessageConverter in Spring MVC in Spring Framework before 3.2.5 and 4.0.0.M1 through 4.0.0.RC1 does not disable external entity resolution, which allows remote attackers to read arbitrary files, cause a denial of service, and conduct CSRF attacks via crafted XML, aka an XML External Entity (XXE) issue, and a different vulnerability than CVE-2013-4152 and CVE-2013-7315.

CVSS v3
—
EG Score
0.0(none)
EPSS
99.8%
KEV
Not listed

Published

January 26, 2014

Last Modified

April 29, 2026

References (14)

Vendor Advisories for CVE-2013-6429(1)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpatch2014-04-14redhat
redhatpatch2014-04-14redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.springframework:spring-web1.0 ... 3.2.4.RELEASE (67 versions)3.2.5.RELEASE—

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 2× in last 7d / 16× 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-07-05 02:55 UTCOSV refresh
  2. 2026-07-04 06:27 UTCEPSS rescore
  3. 2026-06-28 04:53 UTCEPSS rescore
  4. 2026-06-28 04:53 UTCEPSS rescore
  5. 2026-06-24 14:02 UTCEPSS rescore
  6. 2026-06-24 14:02 UTCEPSS rescore
  7. 2026-06-23 21:30 UTCEPSS rescore
  8. 2026-06-23 21:30 UTCEPSS rescore
  9. 2026-06-16 14:39 UTCOSV refresh
  10. 2026-06-15 17:44 UTCEPSS rescore
  11. 2026-06-13 22:57 UTCEPSS rescore
  12. 2026-06-12 23:08 UTCEPSS rescore
  13. 2026-06-11 13:56 UTCEPSS rescore
  14. 2026-06-10 22:15 UTCEPSS rescore
  15. 2026-06-10 13:18 UTCEPSS rescore
  16. 2026-06-08 14:14 UTCEPSS rescore
  17. 2026-06-06 13:45 UTCEPSS rescore
  18. 2026-06-06 13:45 UTCEPSS rescore
  19. 2026-06-05 22:44 UTCEPSS rescore
  20. 2026-06-05 22:44 UTCEPSS rescore
  21. 2026-06-05 06:08 UTCEPSS rescore
  22. 2026-06-05 06:08 UTCEPSS rescore
  23. 2026-06-04 13:09 UTCEPSS rescore
  24. 2026-06-04 13:09 UTCEPSS rescore
  25. 2026-06-02 20:10 UTCEPSS rescore
Show 28 more
  1. 2026-06-02 20:10 UTCEPSS rescore
  2. 2026-05-31 22:28 UTCEPSS rescore
  3. 2026-05-31 22:28 UTCEPSS rescore
  4. 2026-05-31 00:14 UTCEPSS rescore
  5. 2026-05-31 00:14 UTCEPSS rescore
  6. 2026-05-29 13:41 UTCEPSS rescore
  7. 2026-05-29 13:41 UTCEPSS rescore
  8. 2026-05-28 20:36 UTCEG score recompute
  9. 2026-05-28 20:36 UTCVendor advisory
  10. 2026-05-28 13:42 UTCEPSS rescore
  11. 2026-05-28 13:42 UTCEPSS rescore
  12. 2026-05-28 13:42 UTCEPSS rescore
  13. 2026-05-27 13:38 UTCEPSS rescore
  14. 2026-05-27 13:38 UTCEPSS rescore
  15. 2026-05-26 13:41 UTCEPSS rescore
  16. 2026-05-26 13:41 UTCEPSS rescore
  17. 2026-05-26 07:16 UTCEPSS rescore
  18. 2026-05-26 07:16 UTCEPSS rescore
  19. 2026-05-22 21:15 UTCEPSS rescore
  20. 2026-05-22 21:15 UTCEPSS rescore
  21. 2026-05-22 21:15 UTCEPSS rescore
  22. 2026-05-21 22:39 UTCEPSS rescore
  23. 2026-05-20 22:37 UTCEPSS rescore
  24. 2026-05-20 22:37 UTCEPSS rescore
  25. 2026-05-20 11:21 UTCEPSS rescore
  26. 2026-05-20 11:21 UTCEPSS rescore
  27. 2026-05-18 21:29 UTCEPSS rescore
  28. 2026-05-18 21:29 UTCEPSS rescore

Related CVEs(same vendor)

Frequently asked(4)

What is CVE-2013-6429?
CVE-2013-6429 is a none vulnerability published on January 26, 2014. The SourceHttpMessageConverter in Spring MVC in Spring Framework before 3.2.5 and 4.0.0.M1 through 4.0.0.RC1 does not disable external entity resolution, which allows remote attackers to read arbitrary files, cause a denial of service, and conduct CSRF attacks via crafted XML, aka an XML External…
When was CVE-2013-6429 disclosed?
CVE-2013-6429 was first published in the National Vulnerability Database on January 26, 2014, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2013-6429 actively exploited?
CVE-2013-6429 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2013-6429?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2013-6429, 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-2013-6429

Explore →

Is Your Infrastructure Affected by CVE-2013-6429?

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

Start Free Scan →Browse All CVEs