Apicurio Registry is vulnerable to denial of service through XML entity expansion

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

• CISA KEV Not listed.
• EPSS 0.0052, the 44th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

1. 25 Jun 2026, 23:23 UTC Confirmed by the CVE List
2. 26 Jun 2026, 00:32 UTC Confirmed by GitHub Advisory Database
3. 4 Nov 2026, 18:30 UTC Confirmed by OSV

Sources

• GitHub Advisory Database: GHSA-748j-wm96-4wh5
• OSV: GHSA-748j-wm96-4wh5
• nvd.nist.gov/vuln/detail/CVE-2026-12993
• github.com/Apicurio/apicurio-registry/issues/8189
• github.com/Apicurio/apicurio-registry/pull/8200
• github.com/Apicurio/apicurio-registry/commit/03cd1cc081d9b1b4c8b9a59330ff4c980dc68b73
• github.com/Apicurio/apicurio-registry/commit/48369d0e9008f7aab16dce5970c1ecbdd55e9aa5
• access.redhat.com/errata/RHSA-2026:59360
• access.redhat.com/security/cve/CVE-2026-12993
• bugzilla.redhat.com/show_bug.cgi?id=2491692
• github.com/Apicurio/apicurio-registry/releases/tag/3.3.1
• github.com/Apicurio/apicurio-registry/releases/tag/v3.2.6
• github.com/apicurio/apicurio-registry

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.