dbcve.org
Build Of Apicurio RegistryApplication · Redhat

CVE-2026-12993

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-26
Fix available
A fix is available. Upgrade to after 3.2 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apicurio Registry's DocumentBuilderAccessor blocks external DTD and schema access but fails to disable DOCTYPE declarations or enable FEATURE_SECURE_PROCESSING, allowing authenticated attackers with artifact-write permission to upload XML documents containing internal entity-expansion payloads (Billion Laughs variant) that exhaust CPU and heap memory.

MitigationEnable FEATURE_SECURE_PROCESSING and explicitly disable DOCTYPE declarations in the DocumentBuilderFactory configuration to prevent XML entity expansion attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Build Of Apicurio RegistryApplication
Affected:>= 3.0, <= 3.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Apicurio Registry version
    Run 'rpm -q apicurio-registry' or check the product version in the Red Hat package management system
    Affected if Installed version is greater than or equal to 3.0 and less than or equal to 3.2
  2. Verify artifact-write permission is granted
    Review user roles and permissions in the Apicurio Registry authentication/authorization configuration to determine if any non-admin users have artifact-write permissions
    Affected if Users or service accounts have artifact-write permission enabled, allowing XML document uploads
  3. Inspect DocumentBuilderFactory configuration for FEATURE_SECURE_PROCESSING
    Locate the DocumentBuilderAccessor class or configuration file that creates DocumentBuilderFactory instances and verify whether FEATURE_SECURE_PROCESSING is set to true
    Affected if FEATURE_SECURE_PROCESSING is not explicitly set to true or is disabled (null/false)
  4. Inspect DocumentBuilderFactory configuration for DOCTYPE handling
    Locate the DocumentBuilderAccessor class or configuration file and verify whether DOCTYPE declarations are explicitly disallowed via the DISALLOW_DTD feature or equivalent setting
    Affected if DOCTYPE declarations are not explicitly disabled - the factory allows DOCTYPE in uploaded XML documents

You are affected if you run Red Hat Build of Apicurio Registry versions 3.0-3.2, have users with artifact-write permissions, and the DocumentBuilderFactory does not have FEATURE_SECURE_PROCESSING enabled and DOCTYPE declarations disabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 3.2
Interim mitigation

Enable FEATURE_SECURE_PROCESSING and explicitly disable DOCTYPE declarations in the DocumentBuilderFactory configuration to prevent XML entity expansion attacks.

Recommended fix Moderate confidence

3.3.0 or later

  1. Identify the current Apicurio Registry version in use (3.0.x through 3.2.x)
  2. Stop the Apicurio Registry service
  3. Back up the existing database and configuration
  4. Upgrade Apicurio Registry to version 3.3.0 or later
  5. Verify the upgrade by checking release notes for security fixes related to XML entity expansion
  6. Start the service and validate functionality
Caveat Review release notes for any breaking changes between 3.0-3.2 and the target version; minor version upgrades typically have minimal breaking changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Build Of Apicurio Registry Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,780
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-12993 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-12993 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data