EUVD-2026-39577
GHSA-rcmh-vfq7-8gf4
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L
Developer-role auth gives PR:L and network reach AV:N/AC:L; SSRF is primarily a confidentiality/recon primitive (C:L) with scope change (S:C), while integrity/availability impact on internal targets is too situational to assert.
Primary rating from Vendor (redhat).
CVSS VectorVendor: redhat
Lifecycle Timeline
1DescriptionCVE.org
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).
AnalysisAI
Server-side request forgery in Red Hat Build of Apicurio Registry 3 allows a Developer-role user to coerce the registry server into issuing HTTP requests to arbitrary internal URLs. The flaw stems from the WSDLReaderAccessor instantiating a wsdl4j WSDLReader with the javax.wsdl.importDocuments feature left enabled, so a crafted WSDL artifact with attacker-controlled import locations is fetched when content validation runs at FULL strictness. There is no public exploit identified at time of analysis, and the issue is not listed in CISA KEV; CVSS is 7.4 (scope-changed) and exploitation requires authenticated low-privilege access plus a non-default validation setting.
Technical ContextAI
Apicurio Registry is a datastore for API and schema artifacts (OpenAPI, AsyncAPI, Avro, Protobuf, WSDL/XSD) frequently used to govern Kafka and event-driven service contracts. When a WSDL artifact is added, the WSDLReaderAccessor uses the wsdl4j library's WSDLReader to parse and validate the document. wsdl4j supports resolving <wsdl:import> directives, controlled by the javax.wsdl.importDocuments feature; because the accessor never disables this feature, import locations embedded in a submitted WSDL are dereferenced over the network by the server during validation. This is a textbook CWE-918 (SSRF) condition: untrusted input controls the destination of a server-initiated request, and the document-parser/external-entity-style import resolution is the root cause class. The affected component is identified by CPE cpe:2.3:a:red_hat:red_hat_build_of_apicurio_registry_3, i.e. the version 3.x line of the Red Hat distribution.
RemediationAI
No vendor-released patch version is identified in the available data; consult the Red Hat advisory (https://access.redhat.com/security/cve/CVE-2026-12992) and Bugzilla 2491691 (https://bugzilla.redhat.com/show_bug.cgi?id=2491691) for the fixed release and upgrade to it once published. As immediate compensating controls, avoid setting the global or artifact-level VALIDITY rule to FULL for WSDL content (use NONE or SYNTAX_ONLY) since the SSRF only triggers during full validation - the trade-off is reduced schema-import validation coverage. Tighten role assignments so untrusted users do not hold the Developer role, and enable Apicurio's authentication/RBAC if running open. At the network layer, restrict the registry server's egress with an allowlist so it cannot reach internal management endpoints, cloud metadata services (e.g. 169.254.169.254), or other sensitive hosts; the trade-off is that legitimate external WSDL imports will also be blocked. Monitor registry-originated outbound HTTP for anomalous internal destinations.
Server-side request forgery and denial of service in Red Hat Build of Apicurio Registry 3 stem from unsafe XML parsing i
Unauthenticated remote file read in RESTEasy's SourceProvider component allows network attackers to exfiltrate arbitrary
Same weakness CWE-918 – Server-Side Request Forgery (SSRF)
View allVendor StatusVendor
Share
External POC / Exploit Code
Leaving vuln.today