VulnerabilityPublished 17 Mar 2026

CVE-2026-25534: io.spinnaker.clouddriver clouddriver-artifacts · Server-Side Request Forgery (SSRF)

Affects io.spinnaker.clouddriver clouddriver-artifactsSource CVE Database V5

Mentioned vulnerabilities

CVE-2025-61916

Not known to be exploited · CVSS 9.1 Critical · fixed in 2025.4.1 : patch io.spinnaker.clouddriver clouddriver-artifacts as a priority.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

9.1Critical

How severe the flaw is on the 0–10 CVSS scale.

Contested

Critical score, yet low EPSS after six months

EPSS: 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2025.4.1, 2025.3.1, 2025.2.4

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade clouddriver-artifacts and orca-core to 2025.4.1, 2025.3.1 or 2025.2.4; io.spinnaker.clouddriver/clouddriver-artifacts to 2025.2.4.

Affected software

Product	Affected	Fixed in
io.spinnaker.clouddriverclouddriver-artifacts	Affected >=2025.4.0 <2025.4.1	Fixed in 2025.4.1
io.spinnaker.clouddriverclouddriver-artifacts	Affected >=2025.3.0 <2025.3.1	Fixed in 2025.3.1
io.spinnaker.clouddriverclouddriver-artifacts	Affected <2025.2.4	Fixed in 2025.2.4
io.spinnaker.orcaorca-core	Affected >=2025.4.0 <2025.4.1	Fixed in 2025.4.1
io.spinnaker.orcaorca-core	Affected >=2025.3.0 <2025.3.1	Fixed in 2025.3.1
io.spinnaker.orcaorca-core	Affected <2025.2.4	Fixed in 2025.2.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-25534, organizations should promptly apply the official patches released in Spinnaker versions 2025.2.4, 2025.3.1, 2025.4.1, and 2026.0.0, which address the URL validation bypass. Patch management processes should prioritize these updates due to the critical severity. As an immediate workaround, disabling artifact-related features that process user-supplied URLs can reduce exposure until patches are applied. Additionally, organizations should implement strict network segmentation and egress filtering to limit the ability of compromised services to reach sensitive internal resources. Monitoring and logging of outbound requests from clouddriver components can help detect anomalous SSRF attempts. Security teams should audit deployment pipelines for unusual artifact retrieval patterns and validate all user inputs rigorously. Employing Web Application Firewalls (WAFs) with SSRF detection rules can provide an additional layer of defense. Finally, conducting regular security assessments of continuous delivery infrastructure and updating threat models to include SSRF risks will improve long-term resilience.

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.

Impact

The SSRF vulnerability in Spinnaker’s clouddriver-artifacts can have severe consequences for organizations worldwide. By exploiting this flaw, attackers can induce the server to send crafted requests to internal or external systems, potentially bypassing network segmentation and firewall rules. This can lead to unauthorized access to sensitive internal services, leakage of confidential data, and reconnaissance of internal infrastructure. The partial integrity impact means attackers might manipulate artifact retrieval or deployment processes, potentially injecting malicious artifacts or disrupting deployment workflows. Availability impact, though limited, could result from resource exhaustion or denial of service conditions triggered by malicious requests. Organizations using Spinnaker in critical continuous delivery pipelines risk operational disruption and compromise of software supply chain integrity. The vulnerability’s ease of exploitation and high confidentiality impact make it attractive for attackers aiming to escalate privileges or pivot within cloud environments. The lack of required user interaction further increases the threat. Overall, this vulnerability threatens confidentiality, integrity, and availability of deployment pipelines and associated infrastructure, potentially leading to significant operational and reputational damage.

Summary

CVE-2026-25534 is a critical Server-Side Request Forgery (SSRF) vulnerability identified in the io.spinnaker.clouddriver clouddriver-artifacts component of the Spinnaker continuous delivery platform. The vulnerability stems from insufficient URL validation logic that fails to correctly handle underscores in URLs when parsed by Java URL objects. This parsing flaw allows attackers to bypass prior URL validation protections, including those implemented for a previous vulnerability (CVE-2025-61916). The issue affects multiple versions of clouddriver-artifacts prior to patched releases 2025.2.4, 2025.3.1, 2025.4.1, and 2026.0.0. The vulnerability impacts both the clouddriver and Orca components due to shared URL validation logic. Exploiting this SSRF flaw enables an attacker with limited privileges to craft malicious URLs that cause the server to make unauthorized HTTP requests to internal or external resources. This can lead to unauthorized data disclosure, partial service disruption, or further internal network reconnaissance. The vulnerability requires no user interaction and has a low attack complexity, but does require some level of privileges (PR:L). The CVSS v3.1 base score is 9.1, reflecting critical severity with high confidentiality impact, limited integrity impact, and some availability impact. No known exploits have been reported in the wild yet. Spinnaker has released patches in the specified versions to address this issue by improving URL validation logic. As a temporary mitigation, disabling artifact features that process user-supplied URLs can reduce risk. Given Spinnaker’s widespread use in cloud-native continuous delivery pipelines, this vulnerability poses a significant risk to organizations relying on these systems for software deployment and artifact management.

CWE-918Server-Side Request Forgery (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
Implementation · Operation
If there is a known list of applications, IP, hostname, and/or domains to which the product is allowed to communicate, then use allowlists to ensure that outgoing requests are restricted to these known entities. The allowlists could be in the application code or possibly enforced by firewalls or network segmentation.
Implementation · Operation
If the product is expected to be able to connect to arbitrary IP addresses or domains, consider using a denylist that includes private network addresses, internal domain names, etc. The denylist could be in the application code or possibly enforced by firewalls or network segmentation.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Mar 2026, 17:59 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats