How severe is CVE-2010-2227?

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

Which packages are affected by CVE-2010-2227?

CVE-2010-2227 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-2010-2227?

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

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

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is CVE-2010-2227 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2010-2227, including 2 in-the-wild exploitations 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-2010-2227?

CVE-2010-2227 has an EPSS (Exploit Prediction Scoring System) score of 54.8%, 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-2010-2227?

CVE-2010-2227 is classified as Buffer Overflow (CWE-119). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2010-2227 published, and has it been updated?

CVE-2010-2227 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-2010-2227 — tomcat

Fix: apache/tomcat@40e5880

CVE-2010-2227 is a Buffer Overflow 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.

Apache Tomcat does not properly handle an invalid Transfer-Encoding header

Published

May 14, 2022

Updated

Feb 21, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

2 known

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

EPSS Exploitation Probability

via FIRST.org ↗

54.8%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 5.5.0 through 5.5.29, 6.0.0 through 6.0.27, and 7.0.0 beta does not properly handle an invalid Transfer-Encoding header, which allows remote attackers to cause a denial of service (application outage) or obtain sensitive information via a crafted header that interferes with "recycling of a buffer."

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat:tomcat`	≥ 7.0.0&&< 7.0.2	7.0.2`org.apache.tomcat:tomcat:7.0.2`
☕Maven	`org.apache.tomcat:tomcat`	≥ 5.5.0&&< 5.5.30	5.5.30`org.apache.tomcat:tomcat:5.5.30`
☕Maven	`org.apache.tomcat:tomcat`	≥ 6.0.0&&< 6.0.28	6.0.28`org.apache.tomcat:tomcat:6.0.28`

Affected Products

1 product · 55 configurations

Application

tomcatapache

55 versions

5.5.05.5.15.5.25.5.35.5.45.5.55.5.65.5.75.5.85.5.95.5.105.5.11

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.

Apache Tomcat 5.5.0 through 5.5.29, 6.0.0 through 6.0.27, and 7.0.0 beta…

github.comMetasploitOct 2020

Report on github.com

github.comMetasploitMay 2021

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.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2010-2227 is resolved across your whole dependency graph.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

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 HatImportant

Product	Fixed in	Advisory
JBEAP 4.2.0 for RHEL 5	`jbossweb-0:2.0.0-6.CP14.0jpp.ep1.1.el5`	RHSA-2010:0584
JBEWS 1.0 for RHEL 4	`tomcat5-0:5.5.28-9.patch_01.jdk6.ep5.el4`	RHSA-2010:0581
Red Hat Certificate System 7.3	`tomcat5-0:5.5.23-0jpp_4rh.19`	RHSA-2010:0693
Red Hat Developer Suite V.3	`tomcat5-0:5.5.23-0jpp_21rh`	RHSA-2010:0583
Red Hat Enterprise Linux 5	`tomcat5-0:5.5.23-0jpp.9.el5_5`	RHSA-2010:0580
RHAPS Version 2 for RHEL 4	`tomcat5-0:5.5.23-0jpp_4rh.17`	RHSA-2010:0582

Ubuntu

USN-976-1Ubuntu

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2010-2227 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works