CVE-2026-12993VulnerabilityPublished 26 Jun 2026Updated 4 Nov 2026

Io.apicurio:apicurio registry schema util xml: Apicurio Registry is vulnerable to denial of service through XML entity

Affects io.apicurio:apicurio-registry-schema-util-xmlSource GCVE Database

Compare

Authoritative record:CVE-2026-12993· Medium 6.5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 3.3.1 when convenient.

Data as of 4 Nov 2026, 21:27 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.3.1, 3.2.6

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade io.apicurio:apicurio-registry-schema-util-xml to 3.3.1; io.apicurio:apicurio-registry-schema-util-xml to 3.2.6.

Patches and advisories

access.redhat.com/errata/RHSA-2026:59360 (opens in a new tab)

Affected software

Product	Affected	Fixed in
Mavenio.apicurio:apicurio-registry-schema-util-xml	Affected >=3.3.0 <3.3.1	Fixed in 3.3.1
Mavenio.apicurio:apicurio-registry-schema-util-xml	Affected <3.2.6	Fixed in 3.2.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Apply the official patches available in Apicurio Registry versions 3.2.6 and 3.3.1 to remediate this vulnerability. The vendor advisory from Red Hat confirms that these versions contain the fix. No additional mitigations are specified or required beyond applying the update.

Description

Apicurio Registry versions prior to 3.2.6 and from 3.3.0 up to but not including 3.3.1 contain a vulnerability allowing denial of service via XML entity expansion. An attacker with artifact-write permission can upload crafted XML documents with internal entity-expansion payloads (billion-laughs attack) causing CPU and memory exhaustion. The issue arises because DOCTYPE declarations are not disabled and FEATURE_SECURE_PROCESSING is not enabled, despite blocking external DTD and schema access. The JAXP default entity-expansion limit partially mitigates the impact. A fix is available in versions 3.2.6 and 3.3.1.

Impact

Successful exploitation results in denial of service through resource exhaustion (CPU and heap memory) caused by XML entity expansion. There is no impact on confidentiality or integrity. The vulnerability requires low attacker privileges (artifact-write permission) and no user interaction. The attack surface is network accessible. The CVSS v3.1 base score is 6.5 (medium severity) with high availability impact.

CWE-776Improper Restriction of Recursive Entity References in DTDs (Billion Laughs Attack) (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A02:2025: Security Misconfiguration (opens in a new tab)
The product uses XML documents and allows their structure to be defined with a Document Type Definition (DTD), but it does not properly control the number of recursive definitions of entities.
Operation
If possible, prohibit the use of DTDs or use an XML parser that limits the expansion of recursive DTD entities.
Implementation
Before parsing XML files with associated DTDs, scan for recursive entity declarations and do not continue parsing potentially explosive content.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (opens in a new tab)
Attack patterns
Exponential Data Expansion (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Patches and advisories

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2026, 19:58 UTC

WeaknessesCWE-776

Technical details

References

Community reviews

Related threats