How severe is CVE-2022-23437?

CVE-2022-23437 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-23437?

CVE-2022-23437 affects the following packages: xerces:xercesImpl (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-23437?

Update xerces:xercesImpl to 2.12.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-23437 is resolved across your whole dependency graph.

How do I detect CVE-2022-23437 in my Maven dependencies?

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

How do I mitigate CVE-2022-23437 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-2022-23437 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-23437 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-23437?

CVE-2022-23437 has an EPSS (Exploit Prediction Scoring System) score of 11.6%, 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 warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2022-23437?

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

When was CVE-2022-23437 published, and has it been updated?

CVE-2022-23437 was published on January 24, 2022 and was last updated on April 10, 2026. 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

MEDIUM severity

CVE-2022-23437 — xercesImpl

MEDIUM

CVE-2022-23437 is a medium-severity (CVSS 6.5) CWE-835 vulnerability in xerces:xercesImpl. EPSS puts its 30-day exploitation probability at 11.6% (96th percentile). A fix is available for xerces:xercesImpl — see the affected versions and patch details below.

Infinite Loop in Apache Xerces Java

Also known asGHSA-h65f-jvqw-m9fj

Published

Jan 24, 2022

Updated

Apr 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

11.6%probability of exploitation in next 30 days

Moderate 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.

How urgent is this, really

CVE-2022-23437 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,987 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

☕xerces:xercesImpl

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

There's a vulnerability within the Apache Xerces Java (XercesJ) XML parser when handling specially crafted XML document payloads. This causes, the XercesJ XML parser to wait in an infinite loop, which may sometimes consume system resources for prolonged duration. This vulnerability is present within XercesJ version 2.12.1 and the previous versions.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`xerces:xercesImpl`	all versions	2.12.2`xerces:xercesImpl:2.12.2`

Affected Products

29 products · 58 configurations

Application

xerces-japache

≤ 2.12.1

range

Application

active iq unified managernetapp

all

Application

agile engineering data managementoracle

1 version

6.2.1.0

Application

agile product lifecycle managementoracle

1 version

9.3.6

Application

banking deposits and lines of credit servicingoracle

1 version

2.7

Application

banking party managementoracle

1 version

2.7.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for xerces:xercesImpl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update xerces:xercesImpl to 2.12.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-23437 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.

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 JBoss Enterprise Application Platform	`xerces/xercesImpl:2.12.0.SP04-redhat-00001`	RHSA-2022:4922
Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 8	`eap7-xerces-j2-0:2.12.0-3.SP04_redhat_00001.1.el8eap`	RHSA-2022:4919
Red Hat JBoss Enterprise Application Platform 7.4 on RHEL 7	`eap7-xerces-j2-0:2.12.0-3.SP04_redhat_00001.1.el7eap`	RHSA-2022:4918
RHPAM 7.13.1 async	`xercesImpl`	RHSA-2022:6813

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2022-23437 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

CWE Classification

CWE-835CWE-835

Weaponization

No known public exploit tooling found.

Timeline

Disclosed

Jan 24, 2022

Last updated

Apr 10, 2026

Identifiers

CVE-2022-23437

GHSA-h65f-jvqw-m9fj

References

Advisoryopenwall.com Advisorylists.apache.org Advisorysecurity.netapp.com Advisorynvd.nist.gov Fixoracle.com Fixoracle.com Websecurity.netapp.com Packagegithub.com

Related vulnerabilities

Also affects xercesImpl

This CVE is medium severity; 4 of 4 other CVEs affecting xercesImpl are rated as high or higher (top: high).

CVE-2013-4002CVE-2020-14338CVE-2009-2625CVE-2012-0881

Same weakness: CWE-835

This CVE is medium severity; 4 of 4 other CVEs with CWE-835 are rated as high or higher (top: high).

CVE-2026-81876CVE-2026-68523CVE-2026-85715CVE-2026-62949Browse all CWE-835

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedApr 10, 2026

CVE-2022-23437 — xercesImpl

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2022-23437 in your dependencies?