How severe is CVE-2010-4476?

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

Which packages are affected by CVE-2010-4476?

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

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

How do I detect CVE-2010-4476 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-4476 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-2010-4476?

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

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

Yes. There are 1 known exploit references for CVE-2010-4476, including 1 documented proof-of-concept exploit on Exploit-DB. 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-4476?

CVE-2010-4476 has an EPSS (Exploit Prediction Scoring System) score of 23.5%, 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-2010-4476 published, and has it been updated?

CVE-2010-4476 was published on May 14, 2022 and was last updated on February 27, 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-4476 — tomcat

Fix: apache/tomcat@407841c

CVE-2010-4476 is a security 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 affected by infinite loop in Double.parseDouble method in Java Runtime Environment

Published

May 14, 2022

Updated

Feb 27, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

23.5%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs98th percentile — riskier than 98% 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

The Double.parseDouble method in Java Runtime Environment (JRE) in Oracle Java SE and Java for Business 6 Update 23 and earlier, 5.0 Update 27 and earlier, and 1.4.2_29 and earlier, as used in OpenJDK, Apache, JBossweb, and other products, allows remote attackers to cause a denial of service via a crafted string that triggers an infinite loop of estimations during conversion to a double-precision binary floating-point number, as demonstrated using 2.2250738585072012e-308.

Apache Tomcat introduced workarounds to avoid being affected by this issue in versions 7.0.7, 6.0.32, and 5.5.33.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat:tomcat`	≥ 7.0.0&&< 7.0.7	7.0.7`org.apache.tomcat:tomcat:7.0.7`
☕Maven	`org.apache.tomcat:tomcat`	≥ 6.0.0&&< 6.0.32	6.0.32`org.apache.tomcat:tomcat:6.0.32`
☕Maven	`org.apache.tomcat:tomcat`	≥ 5.5.0&&< 5.5.33	5.5.33`org.apache.tomcat:tomcat:5.5.33`

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-35304dosmultiple✓ Verified

Oracle Java - Floating-Point Value Denial of Service

by Konstantin Preisser · Feb 1, 2011

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 7.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2010-4476 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-2010-4476 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2010-4476. 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
Extras for RHEL 4	`java-1.6.0-sun-1:1.6.0.24-1jpp.1.el4`	RHSA-2011:0282
Extras for RHEL 4	`java-1.6.0-ibm-1:1.6.0.9.0-1jpp.4.el4`	RHSA-2011:0290
Extras for RHEL 4	`java-1.5.0-ibm-1:1.5.0.12.3-1jpp.2.el4`	RHSA-2011:0291
Extras for RHEL 4	`java-1.4.2-ibm-0:1.4.2.13.8-1jpp.4.el4`	RHSA-2011:0292
JBEAP 4.2.0 for RHEL 4	`jbossweb-0:2.0.0-8.CP15.patch01.0jpp.ep1.1.el4`	RHSA-2011:0210
JBEWP 5 for RHEL 5	`jbossweb-0:2.1.10-5.patch01.1.1.ep5.el5`	RHSA-2011:0211
JBEWS 1.0 for RHEL 4	`tomcat6-0:6.0.24-11.patch_03.ep5.el4`	RHSA-2011:0348
JBEWS 1.0 for RHEL 4	`tomcat5-0:5.5.28-18_patch_03.ep5.el4`	RHSA-2011:0349

Ubuntu

USN-1079-1Ubuntu USN-1079-2Ubuntu USN-1079-3Ubuntu

Frequently Asked Questions

The `Double.parseDouble` method in Java Runtime Environment (JRE) in Oracle Java SE and Java for Business 6 Update 23 and earlier, 5.0 Update 27 and earlier, and 1.4.2_29 and earlier, as used in OpenJDK, Apache, JBossweb, and other products, allows remote attackers to cause a denial of service via a crafted string that triggers an infinite loop of estimations during conversion to a double-precision binary floating-point number, as demonstrated using 2.2250738585072012e-308. Apache Tomcat introduced workarounds to avoid being affected by this issue in versions 7.0.7, 6.0.32, and 5.5.33.

O3 Security · Impact-Aware SCA

Is CVE-2010-4476 in your dependencies?

O3 Security finds CVE-2010-4476 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