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

Routine

MEDIUM 6.5WATCHLISTUPGRADE

CVE-2026-12993 is a medium-severity flaw (CVSS 6.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 DocumentBuilderAccessor correctly blocks external DTD and schema access but does not disable DOCTYPE declarations or enable FEATURE_SECURE_PROCESSING. An attacker with artifact-write permission can upload XML documents with internal entity-expansion payloads (billion-laughs variant) that cause CPU and heap exhaustion, partially mitigated by the JAXP default 64,000 entity-expansion limit.

Why this priority

On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.5% (top 56%)
CISA exploited list	No
Weakness	CWE-776
Published	2026-06-26
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-26 00:16 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-12993?

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

Is CVE-2026-12993 being exploited?

CVE-2026-12993 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-12993 affect?

CVE-2026-12993 affects build of apicurio registry. Severity is medium (CVSS 6.5). A flaw was found in Apicurio Registry. The DocumentBuilderAccessor correctly blocks external DTD and schema access but does not disable DOCTYPE declarations or enable FEATURE_SECURE_PROCESSING. An attacker with artifact-write permission can

How urgent is CVE-2026-12993?

Priority 39/100. On your watchlist

Related CVEs

CVE-2026-12975 HIGH 8.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