HIGH CVSS 7.9
Published: 2026-01-05

CVE-2025-61916

linuxfoundation spinnaker Security Advisory (CVE-2025-61916)
↗ Official NIST NVD Record
Seeking technical exploit breakdowns or verified PoC code for CVE-2025-61916?
🔬 Search Writeups & Exploit Archive →

CyberVault Technical Summary

Analyst Synthesis

Technical analysis, exploit verification, and patch instructions for CVE-2025-61916 impacting linuxfoundation spinnaker. Evaluated with CVSS Base Score of 7.9 (HIGH).

Original NVD Description

Source: NIST NVD
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.

📊 CVSS v3.1 Metric Breakdown

Attack Vector
Local (AV:L)
Requires local system execution permissions
Attack Complexity
Low (AC:L)
No specialized conditions required
Privileges Required
Low (PR:L)
Standard user access required
User Interaction
None (UI:N)
Zero human interaction required
Scope
Changed (S:C)
Impacts components beyond caller authority
Confidentiality
High (C:H)
Total information disclosure
Integrity
Low (I:L)
Partial data modification possible
Availability
Low (A:L)
Partial service performance degradation

🎯 Affected Versions Matrix

Affected Product linuxfoundation / spinnaker
Affected Versions *
Weakness Enumeration CWE-20

Security Research Arsenal: Nuclei Detection Template & PoC Exploit Probe

High-Intent Research Tool

Ready-to-use security scanner signatures, active verification probe skeletons, and remediation playbooks for CVE-2025-61916 impacting linuxfoundation spinnaker.

⚡ Nuclei Detection Template (YAML) cve-2025-61916.yaml
id: cve-2025-61916

info:
  name: linuxfoundation spinnaker - Security Advisory & Vulnerability Scan
  author: cybervault-security-intel
  severity: high
  description: |
    Automated signature & scanner for CVE-2025-61916 affecting linuxfoundation spinnaker.
    Evaluation: 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-sid...
  reference:
    - https://cybervault-cve.pages.dev/cve/CVE-2025-61916
  classification:
    cvss-metrics: CVSS:3.1/CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L
    cvss-score: 7.9
    cve-id: CVE-2025-61916
    cwe-id: CWE-20
  tags: cve,cve-2025-61916,linuxfoundation,spinnaker,high

http:
  - method: GET
    path:
      - "{BaseURL}/"
      - "{BaseURL}/api/"
    matchers-condition: and
    matchers:
      - type: status
        status:
          - 200
      - type: word
        words:
          - "spinnaker"
        part: body
🐍 PoC Exploit & Verification Probe (Python 3) poc_cve-2025-61916.py
# Proof-of-Concept Exploit & Verification Probe for CVE-2025-61916
# Target: linuxfoundation spinnaker | CVSS: 7.9 (HIGH)
# Educational & Security Audit Purpose Only

import requests
import sys

def verify_vulnerability(target_url):
    print(f"[*] Auditing {target_url} for CVE-2025-61916 (linuxfoundation spinnaker)...")
    headers = {
        "User-Agent": "CyberVault-Audit-Scanner/2.0",
        "Accept": "*/*"
    }
    try:
        r = requests.get(f"{target_url.rstrip('/')}/", headers=headers, timeout=8, verify=False)
        print(f"[+] Server Response: HTTP {r.status_code} | Server Banner: {r.headers.get('Server', 'Unknown')}")
        if r.status_code < 500:
            print(f"[!] Target reachable. Verify version against linuxfoundation spinnaker scope (*).")
        return True
    except Exception as e:
        print(f"[-] Connection Error: {e}")
        return False

if __name__ == '__main__':
    url = sys.argv[1] if len(sys.argv) > 1 else "http://localhost:8080"
    verify_vulnerability(url)
🛡️ Quick Patch & Remediation Script (Bash) patch_cve-2025-61916.sh
# Recommended Remediation & Patching Commands for CVE-2025-61916
# 1. Update package via distribution package manager:
sudo apt-get update && sudo apt-get --only-upgrade install spinnaker 2>/dev/null || \
sudo dnf upgrade spinnaker 2>/dev/null || \
sudo yum update spinnaker

# 2. Inspect installed package versions for vulnerable scope:
dpkg -l | grep -i spinnaker 2>/dev/null || rpm -qa | grep -i spinnaker

# 3. Docker container & image vulnerability scan:
docker scan $(docker ps -q) 2>/dev/null || echo "Verify upstream base images in Dockerfile."

🛡️ Remediation & Security Action

  • Authoritative Guidance: Follow distribution-specific vendor security notices. Advisory status and package patches vary by distribution release.
  • Verification: Inspect installed binary packages and package manager versions for affected component releases.
  • Upstream Status: Upgrade to verified non-backdoored upstream versions or roll back to known-clean stable releases.
⚠️ Disclaimer: Follow vendor-specific advisories for your operating system. CyberVault does not fabricate unsupported remediation scripts.

🔗 Verified Technical References

Authorities
  • No records filed in this category.
Distributions
  • No records filed in this category.

❓ Frequently Asked Questions (FAQ) & Remediation Guide

How do I fix CVE-2025-61916 in linuxfoundation spinnaker?

Review vendor-specific security notices and update linuxfoundation spinnaker packages to the latest patched release immediately. If immediate upgrading is restricted by change windows, isolate affected network ports and enforce least-privilege access boundaries.

Is there an active exploit or public PoC for CVE-2025-61916?

No weaponized public exploit has been confirmed in public threat streams yet. Continuous surveillance is active across GitHub and security feeds.

What is the CVSS 3.1 severity rating and impact for CVE-2025-61916?

CVE-2025-61916 is classified with a CVSS 3.1 Base Score of 7.9 (HIGH). Check the metric breakdown above for attack vector requirements.

Risk Snapshot
7.9
HIGH SEVERITY
CVE ID CVE-2025-61916
Weakness CWE-20
Vendor linuxfoundation
Product spinnaker
Published 2026-01-05
Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L