Skip to content

Spinnaker clouddriver and orca URL validation bypass via underscores in hostnames

Critical severity GitHub Reviewed Published Mar 16, 2026 in spinnaker/spinnaker • Updated Mar 16, 2026

Package

maven io.spinnaker.clouddriver:clouddriver-artifacts (Maven)

Affected versions

< 2025.2.4
>= 2025.3.0, < 2025.3.1
>= 2025.4.0, < 2025.4.1

Patched versions

2025.2.4
2025.3.1
2025.4.1
maven io.spinnaker.orca:orca-core (Maven)
< 2025.2.4
>= 2025.3.0, < 2025.3.1
>= 2025.4.0, < 2025.4.1
2025.2.4
2025.3.1
2025.4.1

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.

References

@jasonmcintosh jasonmcintosh published to spinnaker/spinnaker Mar 16, 2026
Published to the GitHub Advisory Database Mar 16, 2026
Reviewed Mar 16, 2026
Last updated Mar 16, 2026

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L

EPSS score

Weaknesses

Server-Side Request Forgery (SSRF)

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. Learn more on MITRE.

CVE ID

CVE-2026-25534

GHSA ID

GHSA-8r8j-gfhg-fw38

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.