# CVE-2026-25534: Spinnaker clouddriver and orca URL validation bypass via underscores in hostnames > Attackers can bypass URL validation in Spinnaker clouddriver and orca using underscores in hostnames, potentially enabling Server-Side Request Forgery attacks. - **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 17 Mar 2026 - **Updated:** 17 Mar 2026 - **Also known as:** GHSA-8r8j-gfhg-fw38 ## What is CVE-2026-25534? CVE-2026-25534 is a critical server-side request forgery vulnerability in io.spinnaker.clouddriver clouddriver-artifacts, published on 17 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official 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. Weakness: CWE-918 (Server-Side Request Forgery) ## Which versions are affected by CVE-2026-25534? 12 open source packages ship an affected version, including io.spinnaker.clouddriver:clouddriver-artifacts and io.spinnaker.orca:orca-core. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `io.spinnaker.clouddriver:clouddriver-artifacts` | Maven | From 2025.1.6 | 2025.2.4 | | `io.spinnaker.clouddriver:clouddriver-artifacts` | Maven | From 2025.1.6 | 2025.2.4 | | `io.spinnaker.clouddriver:clouddriver-artifacts` | Maven | From 2025.3.0 | 2025.3.1 | | `io.spinnaker.clouddriver:clouddriver-artifacts` | Maven | From 2025.3.0 | 2025.3.1 | | `io.spinnaker.clouddriver:clouddriver-artifacts` | Maven | From 2025.4.0 | 2025.4.1 | | `io.spinnaker.clouddriver:clouddriver-artifacts` | Maven | From 2025.4.0 | 2025.4.1 | | `io.spinnaker.orca:orca-core` | Maven | From 2025.1.6 | 2025.2.4 | | `io.spinnaker.orca:orca-core` | Maven | From 2025.1.6 | 2025.2.4 | | `io.spinnaker.orca:orca-core` | Maven | From 2025.3.0 | 2025.3.1 | | `io.spinnaker.orca:orca-core` | Maven | From 2025.3.0 | 2025.3.1 | | `io.spinnaker.orca:orca-core` | Maven | From 2025.4.0 | 2025.4.1 | | `io.spinnaker.orca:orca-core` | Maven | From 2025.4.0 | 2025.4.1 | ## How do I fix CVE-2026-25534? Upgrade io.spinnaker.clouddriver:clouddriver-artifacts to a fixed version for your release line: 2025.2.4, 2025.3.1 or 2025.4.1. ## Is CVE-2026-25534 being exploited? There is no known exploitation of CVE-2026-25534 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-25534 and fix it if it is affected. What it is: CVE-2026-25534 is a critical server-side request forgery vulnerability in io.spinnaker.clouddriver clouddriver-artifacts, published on 17 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-25534 in the wild and no public exploit code. Affected packages and fixed versions: - io.spinnaker.clouddriver:clouddriver-artifacts (Maven): affected from 2025.1.6; fixed in 2025.2.4 - io.spinnaker.clouddriver:clouddriver-artifacts (Maven): affected from 2025.1.6; fixed in 2025.2.4 - io.spinnaker.clouddriver:clouddriver-artifacts (Maven): affected from 2025.3.0; fixed in 2025.3.1 - io.spinnaker.clouddriver:clouddriver-artifacts (Maven): affected from 2025.3.0; fixed in 2025.3.1 - io.spinnaker.clouddriver:clouddriver-artifacts (Maven): affected from 2025.4.0; fixed in 2025.4.1 - io.spinnaker.clouddriver:clouddriver-artifacts (Maven): affected from 2025.4.0; fixed in 2025.4.1 - io.spinnaker.orca:orca-core (Maven): affected from 2025.1.6; fixed in 2025.2.4 - io.spinnaker.orca:orca-core (Maven): affected from 2025.1.6; fixed in 2025.2.4 - io.spinnaker.orca:orca-core (Maven): affected from 2025.3.0; fixed in 2025.3.1 - io.spinnaker.orca:orca-core (Maven): affected from 2025.3.0; fixed in 2025.3.1 - io.spinnaker.orca:orca-core (Maven): affected from 2025.4.0; fixed in 2025.4.1 - io.spinnaker.orca:orca-core (Maven): affected from 2025.4.0; fixed in 2025.4.1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-25534/ (Markdown: https://insights.sbomify.com/CVE-2026-25534/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-25534 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25534 - OSV: https://osv.dev/vulnerability/CVE-2026-25534 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-25534/ Summaries are generated and may contain mistakes; the official description above is the record.