CVE-2026-12992

Apicurio/apicurio-registry: apicurio-registry: ssrf via wsdl4j import dereference in wsdl full validation

Published Jun 25, 2026 CVSS 3.1 · 7.4 High EPSS < 1% KEV · Not listed
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).

Analysis

AI-generated

Technical impact

The flaw occurs in Apicurio Registry when the WSDLReaderAccessor creates a wsdl4j WSDLReader that still allows the javax.wsdl.importDocuments feature. With VALIDITY set to FULL, an attacker who can upload a WSDL document—by virtue of Developer‑role privileges—can embed attacker-controlled import URLs. The registry then issues HTTP requests to those URLs, giving the attacker access to arbitrary internal addresses. This behavior constitutes a classic SSRF, capable of internal network reconnaissance or data exfiltration, and is classified as CWE‑918.

Affected Systems

The vulnerability affects the Red Hat build of Apicurio Registry version 3, as identified by the CPE cpe:/a:redhat:apicurio_registry:3. Any deployment that permits Developer‑role users to upload WSDL files with FULL validation enabled is vulnerable; no other vendors or product versions are noted.

Risk and Exploitability

The CVSS score of 7.4 signifies a moderate‑high severity with high exploitation difficulty. EPSS data is not available, and the issue is not listed in CISA KE exploitation reports yet. Exploitation requires that the attacker already has Developer‑role access, after which the SSRF can target internal services over HTTP or HTTPS. Consequently, the risk is significant for environments where internal services are exposed and Developer permissions are distributed broadly.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the vendor patch for Apicurio Registry 3 as soon as it is released.
  • Restrict Developer‑role permissions to trusted personnel and consider disabling the ability to upload WSDL files.
  • Configure wsdl4j or the registry to reject or block external import URLs during FULL validation.
  • Enable logging of outbound HTTP requests from the registry and monitor for unexpected destinations.

Generated by OpenCVE AI on June 25, 2026 at 22:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-rcmh-vfq7-8gf4 Apicurio Registry allows upload of WSDL raising HTTP request
History
Type Values Removed Values Added
CPEs cpe:/a:redhat:apicurio_registry:3 cpe:/a:redhat:apicurio_registry:3.3
References
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
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).
Title Apicurio/apicurio-registry: apicurio-registry: ssrf via wsdl4j import dereference in wsdl full validation
First Time appeared Redhat
Redhat apicurio Registry
Weaknesses CWE-918
CPEs cpe:/a:redhat:apicurio_registry:3
Vendors & Products Redhat
Redhat apicurio Registry
References
Metrics cvssV3_1

{'score': 7.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L'}

Weaknesses
  • CWE-918

    Server-Side Request Forgery (SSRF)

Sources

Status
PUBLISHED
Assigner
redhat
Published
Updated
Nov 5, 2026, 2:18 AM
Reserved
Jun 23, 2026, 12:14 PM
Status
Modified
Published
Jun 25, 2026, 10:17 PM
Modified
Oct 25, 2026, 10:10 PM
Severity
Important
Public date
Jun 10, 2026, 1:00 PM