How severe is CVE-2007-5333?

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

Which packages are affected by CVE-2007-5333?

CVE-2007-5333 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-2007-5333?

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

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

Yes. There are 2 known exploit references for CVE-2007-5333, including 1 documented proof-of-concept exploit on Exploit-DB and 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2007-5333?

CVE-2007-5333 has an EPSS (Exploit Prediction Scoring System) score of 62.6%, placing it in the 99th 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. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2007-5333?

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

CVE-2007-5333 was published on May 1, 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

CVE-2007-5333 — tomcat

CVE-2007-5333 is a Information Exposure vulnerability in org.apache.tomcat:tomcat. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.apache.tomcat:tomcat — see the affected versions and patch details below.

Exposure of Sensitive Information in Apache Tomcat

Published

May 1, 2022

Updated

Apr 9, 2025

Affected

3 pkgs

Patched

3 / 3

Exploits

2 known

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

EPSS Exploitation Probability

via FIRST.org ↗

62.6%probability of exploitation in next 30 days

High Risk0.00%

Lower risk than most CVEs99th percentile — riskier than 99% 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 6.0.0 through 6.0.14, 5.5.0 through 5.5.25, and 4.1.0 through 4.1.36 does not properly handle (1) double quote (") characters or (2) %5C (encoded backslash) sequences in a cookie value, which might cause sensitive information such as session IDs to be leaked to remote attackers and enable session hijacking attacks. NOTE: this issue exists because of an incomplete fix for CVE-2007-3385.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat:tomcat`	≥ 6.0.0&&< 6.0.15	6.0.15`org.apache.tomcat:tomcat:6.0.15`
☕Maven	`org.apache.tomcat:tomcat`	≥ 5.5.0&&< 5.5.26	5.5.26`org.apache.tomcat:tomcat:5.5.26`
☕Maven	`org.apache.tomcat:tomcat`	≥ 4.1.0&&< 4.1.37	4.1.37`org.apache.tomcat:tomcat:4.1.37`

Affected Products

1 product · 3 configurations

Application

tomcatapache

≥ 6.0.0 && ≤ 6.0.14

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-31130remotemultiple✓ Verified

Apache Tomcat 6.0.15 - Cookie Quote Handling Remote Information Disclosure

by John Kew · Feb 9, 2008

Exploit-DB Source

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.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2007-5333 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

Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2007-5333 The Red Hat Product Security has rated this issue as having low security impact, a future update may address this flaw.

Product	Fixed in	Advisory
JBEWS 1.0 for RHEL 4	`tomcat5-0:5.5.23-1.patch07.19.ep5.el4`	RHSA-2009:1454
Red Hat Certificate System 7.3	`ant-0:1.6.5-1jpp_1rh`	RHSA-2010:0602
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 Network Satellite Server v 5.2	`tomcat5-0:5.5.23-0jpp_18rh`	RHSA-2009:1616
RHAPS Version 2 for RHEL 4	`tomcat5-0:5.5.23-0jpp_4rh.16`	RHSA-2009:1562

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2007-5333 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works