{"answers":{"affected":"4 open source packages ship an affected version, including io.spinnaker.clouddriver:clouddriver-artifacts. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-61916 in the wild and no public exploit code.","fix":"Upgrade io.spinnaker.clouddriver:clouddriver-artifacts to a fixed version for your release line: 2025.1.6 or 2025.2.3.","what":"CVE-2025-61916 is a high-severity server-side request forgery vulnerability in spinnaker, published on 5 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-61916 and fix it if it is affected.\n\nWhat it is: CVE-2025-61916 is a high-severity server-side request forgery vulnerability in spinnaker, published on 5 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-61916 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- io.spinnaker.clouddriver:clouddriver-artifacts (Maven): affected all versions; fixed in 2025.1.6\n- io.spinnaker.clouddriver:clouddriver-artifacts (Maven): affected all versions; fixed in 2025.1.6\n- io.spinnaker.clouddriver:clouddriver-artifacts (Maven): affected from 2025.2.0; fixed in 2025.2.3\n- io.spinnaker.clouddriver:clouddriver-artifacts (Maven): affected from 2025.2.0; fixed in 2025.2.3\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-61916/ (Markdown: https://insights.sbomify.com/CVE-2025-61916/index.md)","id":"CVE-2025-61916","markdown":"https://insights.sbomify.com/CVE-2025-61916/index.md","name":"CVE-2025-61916","record":{"aliases":["GHSA-vrjc-q2fh-6x9h"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Spinnaker continuous delivery","requires_auth":"low_privilege","summary":"Attackers can exploit improper URL restrictions in Spinnaker to perform server-side request forgery, potentially exposing internal data and credentials.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"spinnaker","vendor":"linuxfoundation"}],"cvss":{"score":7.9,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"},{"id":"CWE-523","name":"Unprotected Transport of Credentials"},{"id":"CWE-20","name":"Improper Input Validation"}],"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Spinnaker vulnerable to SSRF due to improper restrictions on http from user input","id":"CVE-2025-61916","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"ssrf","year":"2025"},"n_packages":4,"n_references":1,"next":{"headline":"n8n Unsafe Buffer Allocation Allows In-Process Memory Disclosure in Task Runner","id":"CVE-2025-61917"},"packages":[{"ecosystem":"Maven","fixed":["2025.1.6"],"introduced":["0"],"last_affected":[],"package":"io.spinnaker.clouddriver:clouddriver-artifacts","purl":null,"source":"GHSA-vrjc-q2fh-6x9h"},{"ecosystem":"Maven","fixed":["2025.1.6"],"introduced":["0"],"last_affected":[],"package":"io.spinnaker.clouddriver:clouddriver-artifacts","purl":"pkg:maven/io.spinnaker.clouddriver/clouddriver-artifacts","source":"GHSA-vrjc-q2fh-6x9h"},{"ecosystem":"Maven","fixed":["2025.2.3"],"introduced":["2025.2.0"],"last_affected":[],"package":"io.spinnaker.clouddriver:clouddriver-artifacts","purl":null,"source":"GHSA-vrjc-q2fh-6x9h"},{"ecosystem":"Maven","fixed":["2025.2.3"],"introduced":["2025.2.0"],"last_affected":[],"package":"io.spinnaker.clouddriver:clouddriver-artifacts","purl":"pkg:maven/io.spinnaker.clouddriver/clouddriver-artifacts","source":"GHSA-vrjc-q2fh-6x9h"}],"prev":{"headline":"OpenPrinting CUPS vulnerable to stack based out-of-bound write","id":"CVE-2025-61915"},"products":["spinnaker"],"published":"2026-01-05","related":[{"cvss_score":10,"headline":"Spinnaker: RCE when using gitrepo artifact types due to improper sanitization of user input on branch and paths","id":"CVE-2026-32604","kev_date_added":null,"published":"2026-04-20"},{"cvss_score":10,"headline":"Spinnaker vulnerable to RCE via expression parsing due to unrestricted context handling","id":"CVE-2026-32613","kev_date_added":null,"published":"2026-04-20"},{"cvss_score":10,"headline":"Improper Access Control in spinnaker","id":"CVE-2021-43832","kev_date_added":null,"published":"2022-01-04"},{"cvss_score":8.8,"headline":"Spinnaker: Non-safe yaml deserialization allowing RCE when using specific types","id":"CVE-2026-44795","kev_date_added":null,"published":"2026-07-10"},{"cvss_score":8.8,"headline":"Code injection in Netflix Spinnaker","id":"CVE-2020-9301","kev_date_added":null,"published":"2020-12-11"},{"cvss_score":7.5,"headline":"Spinnaker: Improper yaml processing on kustomize bake operations","id":"CVE-2026-55175","kev_date_added":null,"published":"2026-07-10"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-05","vendors":["spinnaker"]},"summary":"Attackers can exploit improper URL restrictions in Spinnaker to perform server-side request forgery, potentially exposing internal data and credentials.","url":"https://insights.sbomify.com/CVE-2025-61916/"}