Red Hat Apicurio Registry 3 XML ContentTypeUtil.isParsableXml xml external entity reference

Summaryinfo

A vulnerability has been found in Red Hat Apicurio Registry 3 and classified as problematic. The affected element is the function ContentTypeUtil.isParsableXml of the component XML Handler. This manipulation causes xml external entity reference. This vulnerability appears as CVE-2026-12975. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability was found in Red Hat Apicurio Registry 3. It has been declared as critical. Affected by this vulnerability is the function ContentTypeUtil.isParsableXml of the component XML Handler. The manipulation with an unknown input leads to a xml external entity reference vulnerability. The CWE definition for the vulnerability is CWE-611. The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE 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.

It is possible to read the advisory at access.redhat.com. This vulnerability is known as CVE-2026-12975 since 06/23/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 06/26/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• Red Hat

Name

• Apicurio Registry

Version

• 3

License

• open-source

Website

• Vendor: https://www.redhat.com/

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion