CVE-2026-12975: A flaw was found in Apicurio Registry

This month

HIGH 8.5WATCHLISTUPGRADE

CVE-2026-12975 is a high-severity flaw (CVSS 8.5) affecting build of apicurio registry. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 servic

Why this priority

High severity
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	8.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.4% (top 62%)
CISA exploited list	No
Weakness	CWE-611
Published	2026-06-25
Last modified	2026-10-25

Publisher (CNA): Red Hat, Inc. · Vendor: redhat

Last updated 2026-10-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-06-25 22:17 UTCPublished CVE record published
2026-10-25 22:10 UTCUpdated Record last modified

redhat build of apicurio registry UPGRADE

Affected: >= 3.0 and <= 3.2

Fixed in: newer than 3.2

Safe to downgrade to: a release before 3.0

1. Check installed version

apt-cache policy build-of-apicurio-registry || rpm -q build-of-apicurio-registry || build-of-apicurio-registry --version

2. UPGRADE to newer than 3.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade build-of-apicurio-registry

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade build-of-apicurio-registry

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 3.0 (Debian / Ubuntu)

apt-cache madison build-of-apicurio-registry sudo apt install build-of-apicurio-registry=<VERSION_BEFORE_3.0> sudo apt-mark hold build-of-apicurio-registry

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list build-of-apicurio-registry sudo dnf downgrade build-of-apicurio-registry-<VERSION_BEFORE_3.0> sudo dnf versionlock add build-of-apicurio-registry

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-12975?

build of apicurio registry: upgrade to newer than 3.2. Exact commands for each OS are on this page.

Is CVE-2026-12975 being exploited?

CVE-2026-12975 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-12975 affect?

CVE-2026-12975 affects build of apicurio registry. Severity is high (CVSS 8.5). 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

How urgent is CVE-2026-12975?

Priority 44/100. High severity; On your watchlist

Related CVEs

CVE-2026-12993 MEDIUM 6.5 UPGRADE A flaw was found in Apicurio Registry
CVE-2026-12992 HIGH 7.4 UPGRADE A flaw was found in Apicurio Registry

References

← Back to latest CVEs