SSRF (Server-Side Request Forgery) in io.spinnaker.clouddriver:clouddriver-artifacts (CVE-2026-25534)
Summary
SSRF in io.spinnaker.clouddriver:clouddriver-artifacts (CVE-2026-25534). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2025.2.4 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-25534 has been found in io.spinnaker.clouddriver:clouddriver-artifacts.
Risk of unauthorized operations or information disclosure.
What to do: upgrade io.spinnaker.clouddriver:clouddriver-artifacts to 2025.2.4 or later.
If unsure, ask your IT team or search "io.spinnaker.clouddriver:clouddriver-artifacts CVE-2026-25534" on the vendor's site.
CVE-2026-25534 (io.spinnaker.clouddriver:clouddriver-artifacts) — CWE-918
Patched: 2025.2.4 — apply immediately
Workaround: You can disable the various artifacts on this system to work around these limits.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SSRF (CWE-918) exists in io.spinnaker.clouddriver:clouddriver-artifacts.
Check the vendor advisory for the affected versions of io.spinnaker.clouddriver:clouddriver-artifacts.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2025.2.4.
Workaround: You can disable the various artifacts on this system to work around these limits.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで io.spinnaker.clouddriver:clouddriver-artifacts を使っているサービスとバージョンを洗い出す。
-
2Apply temporary workaround mitigate
You can disable the various artifacts on this system to work around these limits.パッチが適用されるまでの応急処置として、You can disable the various artifacts on this system to work around these limits. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade io.spinnaker.clouddriver:clouddriver-artifacts to 2025.2.4ステージング環境で 2025.2.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com