How severe is CVE-2009-0783?

CVE-2009-0783 has a CVSS score of 4.2/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2009-0783?

CVE-2009-0783 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-2009-0783?

A fix is available for CVE-2009-0783; check the affected-versions list above or the advisory for the patched release of org.apache.tomcat:tomcat, then make sure no transitive dependency still pins the vulnerable range.

How do I detect CVE-2009-0783 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-2009-0783 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-2009-0783 actively exploited in the wild?

No public exploit code has been indexed for CVE-2009-0783 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-2009-0783?

CVE-2009-0783 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 57th 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-2009-0783?

CVE-2009-0783 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-2009-0783 published, and has it been updated?

CVE-2009-0783 was published on May 2, 2022 and was last updated on April 9, 2025. 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

MEDIUM severity

CVE-2009-0783 — tomcat

MEDIUM

CVE-2009-0783 is a medium-severity (CVSS 4.2) 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 2, 2022

Updated

Apr 9, 2025

Affected

3 pkgs

Patched

1 / 3

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs57th percentile — riskier than 57% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

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 4.1.0 through 4.1.39, 5.5.0 through 5.5.27, and 6.0.0 through 6.0.18 permits web applications to replace an XML parser used for other web applications, which allows local users to read or modify the (1) web.xml, (2) context.xml, or (3) tld files of arbitrary web applications via a crafted application that is loaded earlier than the target application.

Affected Packages

3 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat:tomcat`	≥ 4.1.0	No fix
☕Maven	`org.apache.tomcat:tomcat`	≥ 5.5.0	No fix
☕Maven	`org.apache.tomcat:tomcat`	≥ 6.0.0&&< 6.0.20	6.0.20`org.apache.tomcat:tomcat:6.0.20`

Affected Products

1 product · 3 configurations

Application

tomcatapache

≥ 6.0.0 && ≤ 6.0.18

range

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
A fix is available for CVE-2009-0783; check the affected-versions list above or the advisory for the patched release of org.apache.tomcat:tomcat, then make sure no transitive dependency still pins the vulnerable range.
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

Product	Fixed in	Advisory
JBEAP 4.2.0 for RHEL 4	`hibernate3-1:3.2.4-1.SP1_CP08.0jpp.ep1.2.el4`	RHSA-2009:1144
JBEAP 4.2.0 for RHEL 5	`hibernate3-1:3.2.4-1.SP1_CP08.0jpp.ep1.2.3.el5`	RHSA-2009:1143
JBEWS 1.0 for RHEL 4	`tomcat5-0:5.5.23-1.patch07.19.ep5.el4`	RHSA-2009:1454
JBEWS 1.0 for RHEL 4	`tomcat6-0:6.0.18-11.3.ep5.el4`	RHSA-2009:1506
Red Hat Developer Suite V.3	`tomcat5-0:5.5.23-0jpp_18rh`	RHSA-2009:1563
Red Hat Enterprise Linux 5	`tomcat5-0:5.5.23-0jpp.7.el5_3.2`	RHSA-2009:1164
Red Hat JBoss Enterprise Application Platform 4.3 for RHEL 4	`glassfish-jaxb-0:2.1.4-1.11.ep1.el4`	RHSA-2009:1146
Red Hat JBoss Enterprise Application Platform 4.3 for RHEL 5	`glassfish-jaxb-0:2.1.4-1.11.1.ep1.el5`	RHSA-2009:1145

UbuntuMEDIUM

USN-788-1Ubuntu

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2009-0783 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works