CVE-2026-12975

Apicurio Registry utilities allow SSRF and denial of service through XML parsing

A flaw was found in Apicurio Registry. The ContentTypeUtil.isParsableXml() method creates a SAXParserFactory without enabling secure processing features or disabling external entity resolution. An attacker with artifact-write permission (or unauthenticated when the registry runs with default configuration) can upload a crafted XML document to trigger blind server-side request forgery (SSRF) via external DTD/entity fetch, or cause denial of service via entity expansion.

An XML parser processes external entity references in untrusted input, causing the server to fetch internal resources or remote URLs. Typical impact: local file disclosure, server-side request forgery, or denial of service.

CVE-2026-12975 has a CVSS score of 8.5 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.3.1, 3.2.6); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2026-12975? CVE-2026-12975 is a high-severity XML external entity injection (XXE) vulnerability in io.apicurio:apicurio-registry-schema-util-common (maven), affecting versions >= 3.3.0, < 3.3.1. It is fixed in 3.3.1, 3.2.6. An XML parser processes external entity references in untrusted input, causing the server to fetch internal resources or remote URLs.
2. How severe is CVE-2026-12975? CVE-2026-12975 has a CVSS score of 8.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of io.apicurio:apicurio-registry-schema-util-common are affected by CVE-2026-12975? io.apicurio:apicurio-registry-schema-util-common (maven) versions >= 3.3.0, < 3.3.1 is affected.
4. Is there a fix for CVE-2026-12975? Yes. CVE-2026-12975 is fixed in 3.3.1, 3.2.6. Upgrade to this version or later.
5. Is CVE-2026-12975 exploitable, and should I be worried? Whether CVE-2026-12975 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-12975 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-12975?
   • Upgrade io.apicurio:apicurio-registry-schema-util-common to 3.3.1 or later
   • Upgrade io.apicurio:apicurio-registry-schema-util-common to 3.2.6 or later