CVE-2025-61916
Published: 05 January 2026
Summary
CVE-2025-61916 is a high-severity Improper Input Validation (CWE-20) vulnerability in Linuxfoundation Spinnaker. Its CVSS base score is 7.9 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 5.0th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified are NIST 800-53 CM-7 (Least Functionality) and SI-10 (Information Input Validation).
Threat & Defense at a Glance
Threat & Defense Details
Mitigating Controls (NIST 800-53 r5)AI
Directly prevents SSRF by validating user-supplied URLs in artifact providers like HTTP, GitHub, and others to block arbitrary remote data fetches.
Mitigates exploitation by implementing least functionality to disable unnecessary artifact providers such as HTTP accounts that permit arbitrary user URL input.
Remediates the specific SSRF flaw by applying vendor patches to vulnerable Spinnaker versions prior to 2025.1.6, 2025.2.3, and 2025.3.0.
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
SSRF in public-facing Spinnaker directly enables T1190 exploitation; explicit support for fetching AWS IMDSv1/link-local metadata enables T1552.005 credential access.
NVD Description
Spinnaker is an open source, multi-cloud continuous delivery platform. Versions prior to 2025.1.6, 2025.2.3, and 2025.3.0 are vulnerable to server-side request forgery. The primary impact is allowing users to fetch data from a remote URL. This data can be then…
more
injected into spinnaker pipelines via helm or other methods to extract things LIKE idmsv1 authentication data. This also includes calling internal spinnaker API's via a get and similar endpoints. Further, depending upon the artifact in question, auth data may be exposed to arbitrary endpoints (e.g. GitHub auth headers) leading to credentials exposure. To trigger this, a spinnaker installation MUST have two things. The first is an artifact enabled that allows user input. This includes GitHub file artifacts, BitBucket, GitLab, HTTP artifacts and similar artifact providers. JUST enabling the http artifact provider will add a "no-auth" http provider that could be used to extract link local data (e.g. AWS Metadata information). The second is a system that can consume the output of these artifacts. e.g. Rosco helm can use this to fetch values data. K8s account manifests if the API returns JSON can be used to inject that data into the pipeline itself though the pipeline would fail. This vulnerability is fixed in versions 2025.1.6, 2025.2.3, and 2025.3.0. As a workaround, disable HTTP account types that allow user input of a given URL. This is probably not feasible in most cases. Git, Docker and other artifact account types with explicit URL configurations bypass this limitation and should be safe as they limit artifact URL loading. Alternatively, use one of the various vendors which provide OPA policies to restrict pipelines from accessing or saving a pipeline with invalid URLs.
Deeper analysisAI
CVE-2025-61916 is a server-side request forgery (SSRF) vulnerability affecting Spinnaker, an open source, multi-cloud continuous delivery platform. Versions prior to 2025.1.6, 2025.2.3, and 2025.3.0 are vulnerable, enabling unauthorized fetching of data from remote URLs that can be injected into Spinnaker pipelines via methods such as Helm or Kubernetes account manifests.
The vulnerability can be exploited by low-privileged local users (PR:L) in environments where an artifact provider allowing user-supplied URLs is enabled, such as GitHub file artifacts, BitBucket, GitLab, or HTTP artifacts; enabling the HTTP artifact provider alone introduces a no-auth HTTP provider exploitable for link-local data like AWS metadata. A pipeline consumer, such as Rosco for Helm values or Kubernetes manifests processing JSON, must also be present. Attackers can fetch remote data, call internal Spinnaker APIs via GET endpoints, inject extracted data like idmsv1 authentication into pipelines, or expose credentials such as GitHub auth headers to arbitrary endpoints, leading to credential exposure with high confidentiality impact in a changed scope (CVSS 7.9).
The vulnerability is fixed in Spinnaker versions 2025.1.6, 2025.2.3, and 2025.3.0. Advisories recommend disabling HTTP account types that permit user input of arbitrary URLs as a workaround, though this may not be feasible; artifact accounts like Git, Docker, or others with explicit URL configurations are safe as they restrict URL loading. Alternatively, vendors provide OPA policies to restrict pipelines from accessing or saving with invalid URLs. See GHSA-vrjc-q2fh-6x9h for details.
Details
- CWE(s)