How severe is CVE-2011-3190?

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

Which packages are affected by CVE-2011-3190?

CVE-2011-3190 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-2011-3190?

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

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2011-3190?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2011-3190 can be triaged on real exposure rather than presence alone.

Is CVE-2011-3190 actively exploited in the wild?

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

CVE-2011-3190 has an EPSS (Exploit Prediction Scoring System) score of 15.2%, placing it in the 97th 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.

What type of vulnerability is CVE-2011-3190?

CVE-2011-3190 is classified as CWE-264 (CWE-264). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2011-3190 published, and has it been updated?

CVE-2011-3190 was published on May 14, 2022 and was last updated on February 21, 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-2011-3190 — tomcat

Fix: apache/tomcat@a2538ce

CVE-2011-3190 is a CWE-264 vulnerability in org.apache.tomcat:tomcat. 1 public exploit reference exists, so weaponization risk is real. A fix is available for org.apache.tomcat:tomcat — see the affected versions and patch details below.

Apache Tomcat Allows Remote Attackers to Spoof AJP Requests

Published

May 14, 2022

Updated

Feb 21, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

15.2%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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

Certain AJP protocol connector implementations in Apache Tomcat 7.0.0 through 7.0.20, 6.0.0 through 6.0.33, 5.5.0 through 5.5.33, and possibly other versions allow remote attackers to spoof AJP requests, bypass authentication, and obtain sensitive information by causing the connector to interpret a request body as a new request.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat:tomcat`	≥ 7.0.0&&< 7.0.21	7.0.21`org.apache.tomcat:tomcat:7.0.21`
☕Maven	`org.apache.tomcat:tomcat`	≥ 6.0.0&&< 6.0.34	6.0.34`org.apache.tomcat:tomcat:6.0.34`
☕Maven	`org.apache.tomcat:tomcat`	≥ 5.0.0&&< 5.5.34	5.5.34`org.apache.tomcat:tomcat:5.5.34`

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.

Certain AJP protocol connector implementations in Apache Tomcat 7.0.0 th…

issues.apache.orgNVDMar 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.
Fix
Update org.apache.tomcat:tomcat to 7.0.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2011-3190 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2011-3190 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2011-3190. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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 Enterprise Linux 6	`tomcat6-0:6.0.24-35.el6_1`	RHSA-2011:1780
Red Hat JBoss Enterprise Web Server 1 for RHEL 5	`tomcat5-0:5.5.33-27_patch_07.ep5.el5`	RHSA-2012:0680
Red Hat JBoss Enterprise Web Server 1 for RHEL 5	`tomcat6-0:6.0.32-24_patch_07.ep5.el5`	RHSA-2012:0682
Red Hat JBoss Web Server 1.0	see advisory	RHSA-2012:0679
Red Hat JBoss Web Server 1.0	see advisory	RHSA-2012:0681

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2011-3190 in your dependencies?

O3 Security finds CVE-2011-3190 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works