dbcve.org
StoragegridApplication · Netapp

CVE-2025-26515

HIGH · 7.5 CVSS v3.1 Published 2025-09-19
Fix available
A fix is available. Upgrade to 11.8.0.15 / 11.9.0.8 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
StorageGRID (formerly StorageGRID Webscale) versions prior to 11.8.0.15 and 11.9.0.8 without Single Sign-on enabled are susceptible to a Server-Side Request Forgery (SSRF) vulnerability. Successful exploit could allow an unauthenticated attacker to change the password of any Grid Manager or Tenant Manager non-federated user.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a Server-Side Request Forgery (SSRF) vulnerability in NetApp StorageGRID affecting versions prior to 11.8.0.15 and 11.9.0.8 when Single Sign-on (SSO) is not enabled. An unauthenticated attacker can exploit the SSRF to change passwords of any non-federated user in Grid Manager or Tenant Manager, effectively achieving full account takeover.

MitigationUpgrade StorageGRID to version 11.8.0.15 or 11.9.0.8 or later, or enable Single Sign-on (SSO) which mitigates this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
StoragegridApplication
Affected:< 11.8.0.15>= 11.9.0, < 11.9.0.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check StorageGRID version
    Access the Grid Manager, go to Maintenance > System > Software Update, or use the `sudo storagegrid --version` command if you have CLI access. Note the exact version number.
    Affected if The installed version is below 11.8.0.15, or is 11.9.0.x below 11.9.0.8.
  2. Verify SSO configuration status
    In Grid Manager, navigate to Access Control > Identity Federation, or check the Grid Management API endpoint `/api/v3/grid/config/sso`. Determine whether Single Sign-on (SSO) is currently enabled or disabled.
    Affected if SSO is disabled. This is a required condition for the vulnerability to be exploitable.
  3. Identify non-federated local users
    In Grid Manager, go to Access Control > Users, or use the Grid Management API `/api/v3/authorized-users` to list all users. Review the 'federated' attribute for each user to identify local (non-federated) accounts.
    Affected if Non-federated local users exist in the system. These are the targets for password change via the SSRF exploit.

Your environment is affected if the StorageGRID version is vulnerable AND SSO is disabled AND at least one non-federated local user account exists.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 11.8.0.15 / 11.9.0.8 or later
Fixed in 11.8.0.1511.9.0.8
Interim mitigation

Upgrade StorageGRID to version 11.8.0.15 or 11.9.0.8 or later, or enable Single Sign-on (SSO) which mitigates this vulnerability.

Recommended fix High confidence

Upgrade to StorageGRID 11.8.0.15 or later (11.8.x branch), or 11.9.0.8 or later (11.9.x branch)

  1. 1. Identify your current StorageGRID version in the Grid Manager under Maintenance > System > Software Update
  2. 2. Determine which version branch you are on (11.8.x or 11.9.x)
  3. 3. Download the appropriate StorageGRID upgrade package from the NetApp Downloads portal for version 11.8.0.15 or later (if on 11.8.x) or 11.9.0.8 or later (if on 11.9.x)
  4. 4. Review the StorageGRID upgrade procedure in the NetApp documentation before proceeding
  5. 5. Create a support bundle and ensure you have a valid system snapshot/backup
  6. 6. In Grid Manager, navigate to Maintenance > System > Software Update and upload the upgrade file
  7. 7. Run the upgrade following the guided procedure, which will automatically enable SSO if not already configured (note: enabling SSO mitigates this vulnerability but is not required - the version upgrade contains the fix)
  8. 8. After upgrade completes, verify the new version under Grid Manager > Maintenance > System > Software Update > About
Caveat Minor version upgrades typically have low risk; however, always review NetApp release notes for your specific version for any known issues or compatibility considerations before upgrading in production

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Storagegrid Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-26515 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-26515 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data