CVE-2026-12975: Apicurio/apicurio-registry: apicurio-registry: unhardened saxparser in content-type detection leads to blind xxe / ssrf / billion-laughs dos
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-08 00:03 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
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.
Description quoted from the CVE record (assigned by redhat, published 2026-06-25).
Weakness: Improper Restriction of XML External Entity Reference
How it can be exploited
Exploitable over the network with low attack complexity needing low privileges and no user interaction. Impact: confidentiality low, integrity none, availability high. CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:H
CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: partial.
Public exploit evidence (Exploit Observer)
Exploit Observer has no public exploit code naming this CVE. Check Exploit Observer for anything new.
Live scores
- EPSS
- 0.004
low predicted chance of attack - VEDAS
- 0.977
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- No public rule yet
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| Red Hat build of Apicurio Registry 3.3.1 (apicurio/apicurio-registry-rhel8) | Not stated | Not stated |
| Red Hat build of Apicurio Registry 3.3.1 (apicurio/apicurio-registry-rhel9) | Not stated | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
Vendor guidance:
- RHSA-2026:59360 (vendor-advisory, x_refsource_REDHAT)
How to detect it
There is no open VEDAS detection rule for this bug yet. It is listed on the detection gaps page if CISA has confirmed attacks.
References
Vendor advisories and patches
- RHSA-2026:59360 (vendor-advisory, x_refsource_REDHAT)
Technical analysis and advisories
- RHBZ#2491688 (issue-tracking, x_refsource_REDHAT)
Other references
- https://access.redhat.com/security/cve/CVE-2026-12975 (vdb-entry, x_refsource_REDHAT)
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-12975.json (x_sadp-csaf-vex)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.
Supporting partners
