How severe is CVE-2010-2076?

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

Which packages are affected by CVE-2010-2076?

CVE-2010-2076 affects the following packages: org.apache.cxf:cxf-rt-frontend-jaxrs (Maven), org.apache.cxf:cxf-rt-frontend-jaxrs (Maven), org.apache.cxf:cxf-rt-frontend-jaxrs (Maven). Ecosystems affected: Maven.

How do I fix CVE-2010-2076?

Update org.apache.cxf:cxf-rt-frontend-jaxrs to 2.0.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2010-2076 is resolved across your whole dependency graph.

How do I detect CVE-2010-2076 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.cxf:cxf-rt-frontend-jaxrs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2010-2076 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

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

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

CVE-2010-2076 has an EPSS (Exploit Prediction Scoring System) score of 9.8%, placing it in the 96th 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 indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2010-2076?

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

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

CVE-2010-2076 was published on May 13, 2022 and was last updated on December 8, 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-2076 — cxf-rt-frontend-jaxrs

CVE-2010-2076 is a CWE-829 vulnerability in org.apache.cxf:cxf-rt-frontend-jaxrs. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.apache.cxf:cxf-rt-frontend-jaxrs — see the affected versions and patch details below.

Improper Input Validation in Apache CXF

Published

May 13, 2022

Updated

Dec 8, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

9.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs96th percentile — riskier than 96% 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.cxf:cxf-rt-frontend-jaxrs☕org.apache.cxf:cxf-rt-frontend-jaxrs☕org.apache.cxf:cxf-rt-frontend-jaxrs

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 CXF 2.0.x before 2.0.13, 2.1.x before 2.1.10, and 2.2.x before 2.2.9, as used in Apache ServiceMix, Apache Camel, Apache Chemistry, Apache jUDDI, Apache Geronimo, and other products, does not properly reject DTDs in SOAP messages, which allows remote attackers to read arbitrary files, send HTTP requests to intranet servers, or cause a denial of service (CPU and memory consumption) via a crafted DTD, as demonstrated by an entity declaration in a request to samples/wsdl_first_pure_xml, a similar issue to CVE-2010-1632.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.cxf:cxf-rt-frontend-jaxrs`	≥ 2.0.0&&< 2.0.13	2.0.13`org.apache.cxf:cxf-rt-frontend-jaxrs:2.0.13`
☕Maven	`org.apache.cxf:cxf-rt-frontend-jaxrs`	≥ 2.1.0&&< 2.1.10	2.1.10`org.apache.cxf:cxf-rt-frontend-jaxrs:2.1.10`
☕Maven	`org.apache.cxf:cxf-rt-frontend-jaxrs`	≥ 2.2.0&&< 2.2.9	2.2.9`org.apache.cxf:cxf-rt-frontend-jaxrs:2.2.9`

Affected Products

1 product · 3 configurations

Application

cxfapache

≥ 2.2.0 && < 2.2.9

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.

Apache CXF 2.0.x before 2.0.13, 2.1.x before 2.1.10, and 2.2.x before 2.…

svn.apache.orgNVDFeb 2024

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.cxf:cxf-rt-frontend-jaxrs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.cxf:cxf-rt-frontend-jaxrs to 2.0.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2010-2076 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2010-2076 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works