CVE-2025-61916
Spinnaker vulnerable to SSRF due to improper restrictions on http from user input
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 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.
INFO
Published Date :
Jan. 5, 2026, 10:15 p.m.
Last Modified :
Oct. 14, 2026, 7:10 p.m.
Remotely Exploit :
No
Source :
[email protected]
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS | 134c704f-9b21-4f2e-91b3-4a467353bcc0 | |||||
| CVSS 3.1 | HIGH | [email protected] | ||||
| CVSS 3.1 | HIGH | MITRE-CVE | ||||
| CVSS 3.1 | MEDIUM | [email protected] |
Solution
- Update Spinnaker to version 2025.1.6, 2025.2.3, or 2025.3.0.
- Disable HTTP account types allowing user URL input.
- Consider using OPA policies to restrict pipeline URLs.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2025-61916.
| URL | Resource |
|---|---|
| https://github.com/spinnaker/spinnaker/security/advisories/GHSA-vrjc-q2fh-6x9h | Vendor Advisory |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2025-61916 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2025-61916
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2025-61916 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2025-61916 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Translated by [email protected]
Oct. 14, 2026
Action Type Old Value New Value Added Translation Title: Spinnaker, Description: Spinnaker es una plataforma de entrega continua de código abierto y multinube. Las versiones anteriores a 2025.1.6, 2025.2.3 y 2025.3.0 son vulnerables a la falsificación de petición del lado del servidor. El impacto principal es permitir a los usuarios obtener datos de una URL remota. Estos datos pueden ser inyectados en los pipelines de Spinnaker a través de helm u otros métodos para extraer cosas COMO datos de autenticación idmsv1. Esto también incluye llamar a las API internas de Spinnaker a través de un get y puntos finales similares. Además, dependiendo del artefacto en cuestión, los datos de autenticación pueden ser expuestos a puntos finales arbitrarios (p. ej., encabezados de autenticación de GitHub) lo que lleva a la exposición de credenciales. Para activar esto, una instalación de Spinnaker DEBE tener dos cosas. La primera es un artefacto habilitado que permite la entrada del usuario. Esto incluye artefactos de archivo de GitHub, BitBucket, GitLab, artefactos HTTP y proveedores de artefactos similares. SOLO habilitar el proveedor de artefactos http añadirá un proveedor http 'sin autenticación' que podría usarse para extraer datos locales de enlace (p. ej., información de metadatos de AWS). La segunda es un sistema que puede consumir la salida de estos artefactos. p. ej., Rosco helm puede usar esto para obtener datos de valores. Los manifiestos de cuenta de K8s, si la API devuelve JSON, pueden usarse para inyectar esos datos en el propio pipeline, aunque el pipeline fallaría. Esta vulnerabilidad está corregida en las versiones 2025.1.6, 2025.2.3 y 2025.3.0. Como solución alternativa, deshabilite los tipos de cuenta HTTP que permiten la entrada del usuario de una URL dada. Esto probablemente no sea factible en la mayoría de los casos. Git, Docker y otros tipos de cuenta de artefactos con configuraciones de URL explícitas evitan esta limitación y deberían ser seguros ya que limitan la carga de URL de artefactos. Alternativamente, use uno de los varios proveedores que ofrecen políticas OPA para restringir que los pipelines accedan o guarden un pipeline con URL no válidas. -
CVE Modified by [email protected]
Jun. 17, 2026
Action Type Old Value New Value Added Affected [{'vendor': 'spinnaker', 'product': 'spinnaker', 'versions': [{'status': 'affected', 'version': '< 2025.1.6'}, {'status': 'affected', 'version': '>= 2025.2.0, < 2025.2.3'}]}] -
CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0
Jun. 17, 2026
Action Type Old Value New Value Added SSVC {'id': 'CVE-2025-61916', 'role': 'CISA Coordinator', 'options': [{'exploitation': 'none'}, {'automatable': 'no'}, {'technicalImpact': 'partial'}], 'version': '2.0.3', 'timestamp': '2026-01-05T21:29:34.962525Z'} -
Initial Analysis by [email protected]
Feb. 23, 2026
Action Type Old Value New Value Added CVSS V3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L Added CWE CWE-918 Added CPE Configuration OR *cpe:2.3:a:linuxfoundation:spinnaker:*:*:*:*:*:*:*:* versions up to (excluding) 2025.1.6 *cpe:2.3:a:linuxfoundation:spinnaker:*:*:*:*:*:*:*:* versions from (including) 2025.2.0 up to (excluding) 2025.2.3 Added Reference Type GitHub, Inc.: https://github.com/spinnaker/spinnaker/security/advisories/GHSA-vrjc-q2fh-6x9h Types: Vendor Advisory -
New CVE Received by [email protected]
Jan. 05, 2026
Action Type Old Value New Value Added 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 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. Added CVSS V3.1 AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L Added CWE CWE-20 Added CWE CWE-918 Added CWE CWE-523 Added Reference https://github.com/spinnaker/spinnaker/security/advisories/GHSA-vrjc-q2fh-6x9h