How severe is CVE-2026-12992?

CVE-2026-12992 has a CVSS score of 7.4/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2026-12992?

CVE-2026-12992 affects the following packages: io.apicurio:apicurio-registry-schema-util-wsdl (Maven), io.apicurio:apicurio-registry-schema-util-wsdl (Maven). Ecosystems affected: Maven.

How do I fix CVE-2026-12992?

Update io.apicurio:apicurio-registry-schema-util-wsdl to 3.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-12992 is resolved across your whole dependency graph.

How do I detect CVE-2026-12992 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.apicurio:apicurio-registry-schema-util-wsdl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-12992 if there is no patch (or I can't update yet)?

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Is CVE-2026-12992 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-12992 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-12992?

CVE-2026-12992 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 27th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-12992?

CVE-2026-12992 is classified as Server-Side Request Forgery (SSRF) (CWE-918). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-12992 published, and has it been updated?

CVE-2026-12992 was published on June 26, 2026 and was last updated on November 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2026-12992 — apicurio-registry-schema-…

HIGHFix: Apicurio/apicurio-registry#8198

CVE-2026-12992 is a high-severity (CVSS 7.4) Server-Side Request Forgery (SSRF) vulnerability in io.apicurio:apicurio-registry-schema-util-wsdl. A fix is available for io.apicurio:apicurio-registry-schema-util-wsdl — see the affected versions and patch details below.

Apicurio Registry allows upload of WSDL raising HTTP request

Published

Jun 26, 2026

Updated

Nov 4, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-12992.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs27th percentile — riskier than 27% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

☕io.apicurio:apicurio-registry-schema-util-wsdl☕io.apicurio:apicurio-registry-schema-util-wsdl

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

A flaw was found in Apicurio Registry. The WSDLReaderAccessor creates a wsdl4j WSDLReader without disabling the javax.wsdl.importDocuments feature. When the VALIDITY rule is set to FULL, an attacker with Developer-role access can upload a WSDL document containing attacker-controlled import locations, causing the registry to issue HTTP requests to arbitrary internal URLs (server-side request forgery).

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.apicurio:apicurio-registry-schema-util-wsdl`	≥ 3.3.0&&< 3.3.1	3.3.1`io.apicurio:apicurio-registry-schema-util-wsdl:3.3.1`
☕Maven	`io.apicurio:apicurio-registry-schema-util-wsdl`	all versions	3.2.6`io.apicurio:apicurio-registry-schema-util-wsdl:3.2.6`

Affected Products

1 product · 1 configurations

Application

build of apicurio registryredhat

≥ 3.0 && ≤ 3.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.apicurio:apicurio-registry-schema-util-wsdl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.apicurio:apicurio-registry-schema-util-wsdl to 3.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-12992 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Product	Fixed in	Advisory
Red Hat build of Apicurio Registry 3.3.1	`apicurio/apicurio-registry-rhel8`	RHSA-2026:59360

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-12992 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works