How severe is CVE-2005-2090?

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

Which packages are affected by CVE-2005-2090?

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

How do I fix CVE-2005-2090?

The records we use list no patched version of org.apache.tomcat:tomcat for CVE-2005-2090. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2005-2090 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-2005-2090 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2005-2090 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2005-2090, including 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-2005-2090?

CVE-2005-2090 has an EPSS (Exploit Prediction Scoring System) score of 26.1%, placing it in the 98th 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 warrants monitoring and prompt remediation.

When was CVE-2005-2090 published, and has it been updated?

CVE-2005-2090 was published on May 1, 2022 and was last updated on November 8, 2023. 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-2005-2090 — tomcat

CVE-2005-2090 is a security vulnerability in org.apache.tomcat:tomcat. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Tomcat Vulnerable to Web Cache Poisoning

Published

May 1, 2022

Updated

Nov 8, 2023

Affected

2 pkgs

Patched

See advisory

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

26.1%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs98th percentile — riskier than 98% of all scored CVEsHighest risk

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

Real-World Exposure

2 pkgs affected

☕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

Jakarta Tomcat 5.0.19 (Coyote/1.1) and Tomcat 4.1.24 (Coyote/1.0) allows remote attackers to poison the web cache, bypass web application firewall protection, and conduct XSS attacks via an HTTP request with both a "Transfer-Encoding: chunked" header and a Content-Length header, which causes Tomcat to incorrectly handle and forward the body of the request in a way that causes the receiving server to process it as a separate HTTP request, aka "HTTP Request Smuggling."

Affected Packages

2 total

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat:tomcat`	≥ 5.0.0	No fix
☕Maven	`org.apache.tomcat:tomcat`	≥ 4.0.0	No fix

Affected Products

1 product · 2 configurations

Application

tomcatapache

2 versions

4.1.245.0.19

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.

Jakarta Tomcat 5.0.19 (Coyote/1.1) and Tomcat 4.1.24 (Coyote/1.0) allows…

securiteam.comNVDApr 2019

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.
Remediation status
The records we use list no patched version of org.apache.tomcat:tomcat for CVE-2005-2090. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

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 HatModerate

Product	Fixed in	Advisory
Red Hat Certificate System 7.3	`ant-0:1.6.5-1jpp_1rh`	RHSA-2010:0602
Red Hat Developer Suite V.3	`jakarta-commons-modeler-0:2.0-3jpp_3rh`	RHSA-2007:0328
Red Hat Enterprise Linux 5	`jakarta-commons-modeler-0:1.1-8jpp.1.0.2.el5`	RHSA-2007:0327
Red Hat Network Satellite Server v 4.0	`jakarta-commons-pool-0:1.2-2jpp_2rh`	RHSA-2007:1069
Red Hat Network Satellite Server v 4.2	`jabberd-0:2.0s10-3.38.rhn`	RHSA-2008:0524
Red Hat Network Satellite Server v 5.0	`jabberd-0:2.0s10-3.38.rhn`	RHSA-2008:0261
Red Hat Web Application Stack for RHEL 4	`jbossas-0:4.0.5-2.CP04.el4s1.2`	RHSA-2007:0360
RHAPS Version 1 for RHEL 3	`tomcat5-0:5.0.30-0jpp_5rh`	RHSA-2007:0340

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2005-2090 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works