Skip to main content
VulnerabilityPublished

CVE-2026-102495: Apache XMLSchema · CWE-674

Affects Apache XMLSchemaSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 2.3.3 soon.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.3.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade Apache to 2.3.3.

Affected software

ProductAffectedFixed in
Apache Software FoundationApache XMLSchemaAffected
  • <2.3.3
Fixed in
  • 2.3.3
MavenApache Software Foundation/org.apache.ws.xmlschema:xmlschema-corepkg:maven/Apache Software Foundation/org.apache.ws.xmlschema:xmlschema-coreOther threatsAffected
  • <2.3.3
Fixed in
  • 2.3.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Apache XMLSchema to version 2.3.3 or later, which contains the fix for this vulnerability. No other mitigations are indicated or required.

Description

Apache XMLSchema versions before 2.3.3 contain a vulnerability where schema imports and includes can be nested without limit, leading to stack overflow during parsing. This results in a denial of service condition. The issue is fixed in version 2.3.3.

References

Community reviews

Loading reviews…