# CVE-2025-61916: Spinnaker vulnerable to SSRF due to improper restrictions on http from user input

Source: https://junglewise.ai/threats/cve-2025-61916-spinnaker-vulnerable-to-ssrf-due-to-improper-restrictions-on-http  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-01-05  
License: CC BY 4.0 with a link back

CVE-2025-61916 · Severity: high · CVSS 7.9 · Published 2026-01-05

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

Technologies: [Linuxfoundation Spinnaker](https://junglewise.ai/threats/technologies/linuxfoundation-spinnaker). Vendors: [Linuxfoundation](https://junglewise.ai/threats/vendors/linuxfoundation), [Maven](https://junglewise.ai/threats/vendors/maven).

## Quick answers

**Is CVE-2025-61916 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2025-61916 being exploited in the wild.

**How severe is CVE-2025-61916?** High severity, with a CVSS score of 7.9, published 5 January 2026.

**Which products and versions are affected?** io.spinnaker.clouddriver:clouddriver-artifacts (Maven) ECOSYSTEM:introduced=0,fixed=2025.1.6.

**Is there a fix for CVE-2025-61916?** Yes. io.spinnaker.clouddriver:clouddriver-artifacts (Maven): upgrade to 2025.1.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2025-61916?** Check whether you run Linuxfoundation Spinnaker or io.spinnaker.clouddriver:clouddriver-artifacts (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- io.spinnaker.clouddriver:clouddriver-artifacts (Maven): upgrade to 2025.1.6 or later

  ```sh
  # set io.spinnaker.clouddriver:clouddriver-artifacts to 2025.1.6 in your pom.xml or build.gradle
  ```


## Affected products

- Linuxfoundation Spinnaker
- io.spinnaker.clouddriver:clouddriver-artifacts (Maven) ECOSYSTEM:introduced=0,fixed=2025.1.6

## Identifiers

- CVE-2025-61916
- GHSA-vrjc-q2fh-6x9h

## Related threats

- [Spinnaker is an open source, multi-cloud continuous delivery platform. Echo like some other services, uses SPeL (Spring Expression Language)](https://junglewise.ai/threats/cve-2026-32613-spinnaker-rce-via-expression-parsing-due-to-unrestricted-context)
- [Spinnaker: RCE when using gitrepo artifact types due to improper sanitization of user input on branch and paths](https://junglewise.ai/threats/cve-2026-32604-spinnaker-rce-when-using-gitrepo-artifact-types-due-to-improper)
- [Spinnaker clouddriver and orca URL validation bypass via underscores](https://junglewise.ai/threats/cve-2026-25534-spinnaker-clouddriver-and-orca-url-validation-bypass-via)