CVE-2026-25534

Workarounds

You can disable the various artifacts on this system to work around these limits.

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

Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.

CVE-2026-25534 has a CVSS score of 9.1 (Critical). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2025.2.4, 2025.3.1, 2025.4.1); upgrading removes the vulnerable code path.

Kodem intelligence

This has been merged and will be available in versions 2025.4.1, 2025.3.1, 2025.2.4 and 2026.0.0.

1. What is CVE-2026-25534? CVE-2026-25534 is a critical-severity server-side request forgery (SSRF) vulnerability in io.spinnaker.clouddriver:clouddriver-artifacts (maven), affecting versions < 2025.2.4. It is fixed in 2025.2.4, 2025.3.1, 2025.4.1. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
2. How severe is CVE-2026-25534? CVE-2026-25534 has a CVSS score of 9.1 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2026-25534?
   • io.spinnaker.clouddriver:clouddriver-artifacts (maven) (versions < 2025.2.4)
   • io.spinnaker.orca:orca-core (maven) (versions < 2025.2.4)
4. Is there a fix for CVE-2026-25534? Yes. CVE-2026-25534 is fixed in 2025.2.4, 2025.3.1, 2025.4.1. Upgrade to this version or later.
5. Is CVE-2026-25534 exploitable, and should I be worried? Whether CVE-2026-25534 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-25534 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-25534?
   • Upgrade io.spinnaker.clouddriver:clouddriver-artifacts to 2025.2.4 or later
   • Upgrade io.spinnaker.clouddriver:clouddriver-artifacts to 2025.3.1 or later
   • Upgrade io.spinnaker.clouddriver:clouddriver-artifacts to 2025.4.1 or later
   • Upgrade io.spinnaker.orca:orca-core to 2025.2.4 or later
   • Upgrade io.spinnaker.orca:orca-core to 2025.3.1 or later
   • Upgrade io.spinnaker.orca:orca-core to 2025.4.1 or later