CVE-2026-12992
Analyzed Analyzed - Analysis Complete

Apicurio Registry SSRF via WSDL Import in FULL Validity Mode

Vulnerability report for CVE-2026-12992, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-06-25

Last updated on: 2026-07-15

Assigner: Red Hat, Inc.

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).

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-06-25
Last Modified
2026-07-15
Generated
2026-07-16
AI Q&A
2026-06-26
EPSS Evaluated
2026-07-15
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
redhat build_of_apicurio_registry From 3.0 (inc) to 3.2 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability exists in Apicurio Registry where the WSDLReaderAccessor creates a wsdl4j WSDLReader without disabling the javax.wsdl.importDocuments feature.

When the VALIDITY rule is set to FULL, an attacker who has Developer-role access can upload a WSDL document that contains attacker-controlled import locations.

This causes the registry to make HTTP requests to arbitrary internal URLs, resulting in a server-side request forgery (SSRF) vulnerability.

Detection Guidance

This vulnerability involves the Apicurio Registry issuing HTTP GET requests to arbitrary internal URLs when processing malicious WSDL files with the VALIDITY rule set to FULL. Detection can focus on monitoring unusual outbound HTTP requests from the registry server to internal or unexpected endpoints.

You can detect exploitation attempts by inspecting logs for HTTP requests initiated by the Apicurio Registry to internal services or cloud metadata endpoints that are not normally accessed.

Additionally, monitoring for uploads of WSDL files containing suspicious import locations by users with Developer-role access can help identify potential exploitation.

Specific commands are not provided in the resources, but general network monitoring tools like tcpdump or Wireshark can be used to capture outbound HTTP traffic from the registry server. For example:

  • tcpdump -i <interface> -nn -s0 -A port 80 or port 443
  • grep or analyze Apicurio Registry logs for HTTP requests to internal IP ranges or unusual domains.
Impact Analysis

An attacker with Developer-role access can exploit this vulnerability to make the Apicurio Registry server send HTTP requests to internal URLs that the attacker controls.

This can lead to unauthorized access to internal systems, potential data leakage, or further attacks within the internal network.

The CVSS score of 7.4 indicates a high severity impact affecting confidentiality, integrity, and availability.

Compliance Impact

The vulnerability allows an attacker with Developer-role access to perform server-side request forgery (SSRF) by uploading malicious WSDL documents that cause the registry to make HTTP requests to arbitrary internal URLs. This can lead to unauthorized access or exposure of internal services and potentially sensitive data.

Such unauthorized internal requests and potential data exposure could negatively impact compliance with standards and regulations like GDPR and HIPAA, which require strict controls over data access and protection of sensitive information.

However, the provided information does not explicitly discuss compliance impacts or specific regulatory consequences.

Mitigation Strategies

The immediate mitigation is to disable the import dereference feature in the WSDLReader used by Apicurio Registry.

Specifically, the following features should be disabled in the WSDLReader configuration:

  • wsdlReader.setFeature("javax.wsdl.importDocuments", false)
  • wsdlReader.setFeature("com.ibm.wsdl.parseXMLSchemas", false)

Long-term recommendations include replacing the unmaintained wsdl4j library with a maintained alternative like Apache Woden or restricting WSDL validation to SYNTAX_ONLY level to prevent recursive fetching of imports.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-12992. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart