Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:LCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-25534 is a critical-severity SSRF (CWE-918) vulnerability. Its CVSS base score is 9.1 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 35th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-4 (Information Flow Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-25534 is a URL validation bypass vulnerability in Netflix's Spinnaker platform, specifically affecting the clouddriver and Orca components. Spinnaker's updated URL validation logic for user-inputted URLs in clouddriver failed to properly handle underscores during parsing by Java URL objects, enabling a bypass of mitigations for the prior CVE-2025-61916 via crafted URLs. The issue also extends to Orca's existing fromUrl expression handling, impacting both artifacts and classified under CWE-918 (Server-Side Request Forgery).
Attackers with low privileges (PR:L) can exploit this over the network (AV:N) with low complexity (AC:L) and no user interaction (UI:N), achieving scope-crossing effects (S:C). This yields high confidentiality impact (C:H), along with low integrity (I:L) and availability (I:L) impacts, for an overall CVSS v3.1 score of 9.1. Exploitation relies on supplying malicious URLs that evade sanitation, potentially allowing unauthorized actions tied to the bypassed prior vulnerability.
Patches addressing this vulnerability have been merged and are available in Spinnaker versions 2025.4.1, 2025.3.1, 2025.2.4, and 2026.0.0. As a workaround, administrators can disable the affected clouddriver and Orca artifacts. Additional details are provided in GitHub security advisories GHSA-8r8j-gfhg-fw38 and GHSA-vrjc-q2fh-6x9h, as well as commit 7c4737906239a958a468e843239c6785b03d0eda.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-12592
Vulnerability Data
### Impact Spinnaker updated URL Validation logic on user input to provide sanitation on user inputted URLs for clouddriver. However, they missed that Java URL objects do not correctly handle underscores on parsing. This led to a bypass of the…
more
previous CVE (CVE-2025-61916) through the use of carefully crafted URLs. Note, Spinnaker found this not just in that CVE, but in the existing URL validations in Orca fromUrl expression handling. This CVE impacts BOTH artifacts as a result. ### Patches This has been merged and will be available in versions 2025.4.1, 2025.3.1, 2025.2.4 and 2026.0.0. ### Workarounds You can disable the various artifacts on this system to work around these limits.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.3.6V1.5.3V5.3.2V10.4.7
Mitigating Controls (NIST 800-53 r5) AI
Information flow enforcement can restrict which destinations the server is allowed to contact on behalf of users.
Input validation directly stops untrusted URLs from being accepted and fetched without destination checks.
Boundary protection limits the network reach of server-initiated requests even if SSRF occurs.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure development practices directly include input validation and destination allow-listing that prevent SSRF.
Runtime monitoring of web applications and services can detect anomalous outbound requests indicative of SSRF.
Vulnerability identification processes can discover and record SSRF flaws in web applications.
Network segmentation and egress controls can limit the damage from successful SSRF requests.