Redhat Build Of Apicurio Registry
CVE-2026-12975
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.
What this means for your business
- It affects Redhat Build Of Apicurio Registry. It matters if your company, or a supplier that handles your data, runs it.
- An attacker can use it remotely, over a network, with an ordinary user login, and without anyone at your company clicking anything.
- FIRST's prediction model gives it a 0.4% chance of attack attempts being seen in the next 30 days, ranking above 36% of all known flaws.
What to do
- 1Check whether your company or your suppliers run Redhat Build Of Apicurio Registry, and which version. The affected versions are listed further down this page.
- 2If you do, apply the vendor's fix. A patch or vendor advisory has been published.
Not sure if your company is exposed?
Fastnexa’s certified penetration testers can check whether attackers could use this flaw, or others like it, against your websites, apps and network. The full test is free for our first 10 founding clients until 31 December 2026.
Scoring
- CVSS
- 8.5 (v3.1)
- Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:H- Weakness
- CWE-611
- Assigned by
- secalert@redhat.com
Dates
- Published
- 2026-06-25
- Last modified
- 2026-08-26
- Sources
- NVD
Affected products
- Redhat Build Of Apicurio Registry3.0 - 3.2
As listed in the NVD configuration data. Not a statement about your estate.