Apicurio Registry utilities allow SSRF and denial of service through XML parsing
CVE-2026-12975GHSA-7g64-f2hm-vjxp
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (io.apicurio:apicurio-registry-schema-util-common 3.3.1, 3.2.6), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Maven io.apicurio:apicurio-registry-schema-util-common
- Affected
- >= 3.3.0, < 3.3.1< 3.2.6
- Fixed in
- 3.3.1, 3.2.6
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-7g64-f2hm-vjxp lists affected ranges: Maven io.apicurio:apicurio-registry-schema-util-common >=3.3.0 =0 <3.2.6
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-7g64-f2hm-vjxp lists affected ranges: Maven io.apicurio:apicurio-registry-schema-util-common >=3.3.0 =0 <3.2.6 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 8.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:H
- EPSS
- CVE-2026-12975: 0.44% estimated exploitation activity in the next 30 days; percentile 38.30 (FIRST EPSS, 2026-11-10). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
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 service via entity expansion.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from osv record GHSA-7g64-f2hm-vjxp
- Revision 1 · created ·
Published from ghsa record GHSA-7g64-f2hm-vjxp
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-12975 Advisory: Apicurio Registry utilities allow SSRF and denial of service through XML parsing IDs: CVE-2026-12975, GHSA-7g64-f2hm-vjxp Record: https://patchnext.com/advisories/cve-2026-12975 (revision 2, source checked 5 Nov 2026, 06:40 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 8.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: io.apicurio:apicurio-registry-schema-util-common 3.3.1, 3.2.6. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven io.apicurio:apicurio-registry-schema-util-common: affected >= 3.3.0, < 3.3.1; < 3.2.6; fixed in 3.3.1, 3.2.6 ## Suggested inspection (read-only) - Maven io.apicurio:apicurio-registry-schema-util-common: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on io.apicurio:apicurio-registry-schema-util-common. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-7g64-f2hm-vjxp (GitHub-reviewed advisory GHSA-7g64-f2hm-vjxp lists affected ranges: Maven io.apicurio:apicurio-registry-schema-util-common >=3.3.0 =0 <3.2.6) - Verified: https://osv.dev/vulnerability/GHSA-7g64-f2hm-vjxp (OSV record GHSA-7g64-f2hm-vjxp lists affected ranges: Maven io.apicurio:apicurio-registry-schema-util-common >=3.3.0 =0 <3.2.6 (fixed)) Commands are suggestions: review each one before running it.
Loading voting…