How severe is CVE-2013-4590?

No CVSS score has been assigned to CVE-2013-4590 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2013-4590?

CVE-2013-4590 affects the following packages: org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven). Ecosystems affected: Maven.

How do I fix CVE-2013-4590?

Update org.apache.tomcat:tomcat to 6.0.39 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-4590 is resolved across your whole dependency graph.

How do I detect CVE-2013-4590 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2013-4590 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2013-4590 actively exploited in the wild?

No public exploit code has been indexed for CVE-2013-4590 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2013-4590?

CVE-2013-4590 has an EPSS (Exploit Prediction Scoring System) score of 9.5%, placing it in the 95th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2013-4590?

CVE-2013-4590 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2013-4590 published, and has it been updated?

CVE-2013-4590 was published on May 14, 2022 and was last updated on November 28, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2013-4590 — tomcat

Fix: apache/tomcat@05c84ff

CVE-2013-4590 is a Information Exposure vulnerability in org.apache.tomcat:tomcat. A fix is available for org.apache.tomcat:tomcat — see the affected versions and patch details below.

Exposure of Sensitive Information to an Unauthorized Actor in Apache Tomcat

Published

May 14, 2022

Updated

Nov 28, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2013-4590.

EPSS Exploitation Probability

via FIRST.org ↗

9.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs95th percentile — riskier than 95% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected

☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Apache Tomcat before 6.0.39, 7.x before 7.0.50, and 8.x before 8.0.0-RC10 allows attackers to obtain "Tomcat internals" information by leveraging the presence of an untrusted web application with a context.xml, web.xml, *.jspx, *.tagx, or *.tld XML document containing an external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) issue.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat:tomcat`	all versions	6.0.39`org.apache.tomcat:tomcat:6.0.39`
☕Maven	`org.apache.tomcat:tomcat`	≥ 7.0.0&&< 7.0.50	7.0.50`org.apache.tomcat:tomcat:7.0.50`
☕Maven	`org.apache.tomcat:tomcat`	≥ 8.0.0-RC1&&< 8.0.0-RC10	8.0.0-RC10`org.apache.tomcat:tomcat:8.0.0-RC10`

Affected Products

3 products · 193 configurations

Application

tomcatapache

≤ 6.0.37

173 versions

1.1.33.03.13.1.13.23.2.13.2.23.2.33.2.43.33.3.13.3.1a

debian linuxdebian

1 version

7.0

solarisoracle

1 version

11.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.tomcat:tomcat to 6.0.39 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-4590 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatLow

This issue did not affect JBoss Web, as shipped with various Red Hat JBoss products. This issue does affect Tomcat 5 as shipped by Red Hat Enterprise Linux 5. The risks in breaking compatibility associated with fixing this flaw outweigh the benefits of the fix, therefore Red Hat does not plan to fix this flaw in Red…

Product	Fixed in	Advisory
Red Hat Enterprise Linux 6	`tomcat6-0:6.0.24-78.el6_5`	RHSA-2014:1038
Red Hat JBoss Enterprise Web Server 2 for RHEL 5	`antlr-eap6-0:2.7.7-17.redhat_4.1.ep6.el5`	RHSA-2014:1088
Red Hat JBoss Enterprise Web Server 2 for RHEL 6	`antlr-eap6-0:2.7.7-17.redhat_4.1.ep6.el6`	RHSA-2014:1087
Red Hat JBoss Web Server 2.1	`tomcat6`	RHSA-2014:1086

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2013-4590 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works