Missing XML Validation in Apache Xerces2

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

• CVE-2013-4002: 24.74% estimated exploitation activity in the next 30 days; percentile 97.90 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

XMLscanner.java in Apache Xerces2 Java Parser before 2.12.0, as used in the Java Runtime Environment (JRE) in IBM Java 5.0 before 5.0 SR16-FP3, 6 before 6 SR14, 6.0.1 before 6.0.1 SR6, and 7 before 7 SR5 as well as Oracle Java SE 7u40 and earlier, Java SE 6u60 and earlier, Java SE 5.0u51 and earlier, JRockit R28.2.8 and earlier, JRockit R27.7.6 and earlier, Java SE Embedded 7u40 and earlier, and possibly other products allows remote attackers to cause a denial of service via vectors related to XML attribute names.

Published by the source

13 May 2022, 01:01 UTC

Last modified by the source

5 Mar 2024, 17:50 UTC

Source last checked

26 Oct 2026, 16:29 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-7j4h-8wpf-rqfh

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2013-4002

Advisory: Missing XML Validation in Apache Xerces2
IDs: CVE-2013-4002, GHSA-7j4h-8wpf-rqfh
Record: https://patchnext.com/advisories/cve-2013-4002 (revision 1, source checked 26 Oct 2026, 16:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: xerces:xercesImpl 2.12.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven xerces:xercesImpl: affected < 2.12.0; fixed in 2.12.0

## Suggested inspection (read-only)
- Maven xerces:xercesImpl: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on xerces:xercesImpl.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-7j4h-8wpf-rqfh (GitHub-reviewed advisory GHSA-7j4h-8wpf-rqfh lists affected ranges: Maven xerces:xercesImpl >=0 <2.12.0)

Commands are suggestions: review each one before running it.