CVE-2026-25534 is a critical-severity (CVSS 9.1) Server-Side Request Forgery (SSRF) vulnerability in io.spinnaker.clouddriver:clouddriver-artifacts. A fix is available for io.spinnaker.clouddriver:clouddriver-artifacts — see the affected versions and patch details below.
Spinnaker clouddriver and orca URL validation bypass via underscores in hostnames
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-25534.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2026-25534 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
io.spinnaker.clouddriver:clouddriver-artifacts☕io.spinnaker.clouddriver:clouddriver-artifacts☕io.spinnaker.clouddriver:clouddriver-artifacts☕io.spinnaker.orca:orca-core☕io.spinnaker.orca:orca-core☕io.spinnaker.orca:orca-coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
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 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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.spinnaker.clouddriver:clouddriver-artifacts | ≥ 2025.1.6&&< 2025.2.4 | 2025.2.4io.spinnaker.clouddriver:clouddriver-artifacts:2025.2.4 |
| ☕Maven | io.spinnaker.clouddriver:clouddriver-artifacts | ≥ 2025.3.0&&< 2025.3.1 | 2025.3.1io.spinnaker.clouddriver:clouddriver-artifacts:2025.3.1 |
| ☕Maven | io.spinnaker.clouddriver:clouddriver-artifacts | ≥ 2025.4.0&&< 2025.4.1 | 2025.4.1io.spinnaker.clouddriver:clouddriver-artifacts:2025.4.1 |
| ☕Maven | io.spinnaker.orca:orca-core | ≥ 2025.1.6&&< 2025.2.4 | 2025.2.4io.spinnaker.orca:orca-core:2025.2.4 |
| ☕Maven | io.spinnaker.orca:orca-core | ≥ 2025.3.0&&< 2025.3.1 | 2025.3.1io.spinnaker.orca:orca-core:2025.3.1 |
| ☕Maven | io.spinnaker.orca:orca-core | ≥ 2025.4.0&&< 2025.4.1 | 2025.4.1io.spinnaker.orca:orca-core:2025.4.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.spinnaker.clouddriver:clouddriver-artifacts, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.spinnaker.clouddriver:clouddriver-artifacts to 2025.2.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-25534 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-25534 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2026-25534. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-25534 in your dependencies?
O3 Security finds CVE-2026-25534 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.