CVE-2026-12975 is a high-severity (CVSS 8.5) XML External Entity (XXE) vulnerability in io.apicurio:apicurio-registry-schema-util-common. A fix is available for io.apicurio:apicurio-registry-schema-util-common — see the affected versions and patch details below.
Apicurio Registry utilities allow SSRF and denial of service through XML parsing
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-12975.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
io.apicurio:apicurio-registry-schema-util-common☕io.apicurio:apicurio-registry-schema-util-commonReal-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
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.apicurio:apicurio-registry-schema-util-common | ≥ 3.3.0&&< 3.3.1 | 3.3.1io.apicurio:apicurio-registry-schema-util-common:3.3.1 |
| ☕Maven | io.apicurio:apicurio-registry-schema-util-common | all versions | 3.2.6io.apicurio:apicurio-registry-schema-util-common:3.2.6 |
Affected Products
build of apicurio registryredhatDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.apicurio:apicurio-registry-schema-util-common, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.apicurio:apicurio-registry-schema-util-common to 3.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-12975 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.
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.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat build of Apicurio Registry 3.3.1 | apicurio/apicurio-registry-rhel8 | RHSA-2026:59360 |
Frequently Asked Questions
Is CVE-2026-12975 in your dependencies?
Find it across Maven, including transitive dependencies.