How severe is CVE-2026-25534?

CVE-2026-25534 has a CVSS score of 9.1/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2026-25534?

CVE-2026-25534 affects the following packages: io.spinnaker.clouddriver:clouddriver-artifacts (Maven), io.spinnaker.clouddriver:clouddriver-artifacts (Maven), io.spinnaker.clouddriver:clouddriver-artifacts (Maven), io.spinnaker.orca:orca-core (Maven), io.spinnaker.orca:orca-core (Maven), io.spinnaker.orca:orca-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2026-25534?

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.

How do I detect CVE-2026-25534 in my Maven dependencies?

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.

How do I mitigate CVE-2026-25534 if there is no patch (or I can't update yet)?

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Is CVE-2026-25534 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-25534 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-25534?

CVE-2026-25534 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 18th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-25534?

CVE-2026-25534 is classified as Server-Side Request Forgery (SSRF) (CWE-918). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-25534 published, and has it been updated?

CVE-2026-25534 was published on March 17, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

CRITICAL severity

CVE-2026-25534 — clouddriver-artifacts

CRITICALFix: spinnaker/spinnaker@7c47379

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

Also known asGHSA-8r8j-gfhg-fw38

Published

Mar 17, 2026

Updated

Oct 28, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

None indexed

Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk+0.00%

Lower risk than most CVEs18th percentile — riskier than 18% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

6 pkgs affected

☕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-core

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

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.spinnaker.clouddriver:clouddriver-artifacts`	≥ 2025.1.6&&< 2025.2.4	2025.2.4`io.spinnaker.clouddriver:clouddriver-artifacts:2025.2.4`
☕Maven	`io.spinnaker.clouddriver:clouddriver-artifacts`	≥ 2025.3.0&&< 2025.3.1	2025.3.1`io.spinnaker.clouddriver:clouddriver-artifacts:2025.3.1`
☕Maven	`io.spinnaker.clouddriver:clouddriver-artifacts`	≥ 2025.4.0&&< 2025.4.1	2025.4.1`io.spinnaker.clouddriver:clouddriver-artifacts:2025.4.1`
☕Maven	`io.spinnaker.orca:orca-core`	≥ 2025.1.6&&< 2025.2.4	2025.2.4`io.spinnaker.orca:orca-core:2025.2.4`
☕Maven	`io.spinnaker.orca:orca-core`	≥ 2025.3.0&&< 2025.3.1	2025.3.1`io.spinnaker.orca:orca-core:2025.3.1`
☕Maven	`io.spinnaker.orca:orca-core`	≥ 2025.4.0&&< 2025.4.1	2025.4.1`io.spinnaker.orca:orca-core:2025.4.1`

Detection & mitigation playbook

Open-source dependency

Detect
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
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

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