CVE-2025-26517
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 · uneditedStorageGRID (formerly StorageGRID Webscale) versions prior to 11.8.0.15 and 11.9.0.8 are susceptible to a privilege escalation vulnerability. Successful exploit could allow an unauthorized authenticated attacker to discover Grid node names and IP addresses or modify Storage Grades.
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 · moderate confidenceThis is a privilege escalation vulnerability in NetApp StorageGRID. An authenticated attacker with limited (unauthorized) privileges can escalate to discover Grid node names and IP addresses (information disclosure) or modify Storage Grades (data modification). The vulnerability stems from improper authorization checks allowing authenticated users to access administrative functions they should not have permission to perform.
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< 11.8.0.15>= 11.9.0, < 11.9.0.8CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed StorageGRID versionLog into the Grid Manager and navigate to Maintenance > System > Software Update, or use the `sudo storagegrid --version` command on the admin node. Alternatively, check the /var/local/lib/original/sgws-install/version file on the primary admin node.Affected if The installed version is less than 11.8.0.15, or is 11.9.0.x where x is less than 8 (for example 11.9.0.0 through 11.9.0.7).
-
Identify user accounts with limited privilegesIn Grid Manager, go to Access Control > Users and review all user accounts. Note any accounts assigned to roles other than Administrator (such as Read-Only, Tenant User, or custom roles with restricted permissions).Affected if There exist authenticated non-administrator user accounts in the system.
-
Review audit logs for unauthorized administrative actionsIn Grid Manager, go to Support > Audit. Search for events indicating administrative operations performed by non-administrator accounts. Look for audit codes related to node discovery (NMGT, NMON) or Storage Grade modifications (SGRP, SSMS).Affected if Audit logs show administrative functions (node information retrieval, Storage Grade modifications) performed by users without Administrator role.
-
Check for unauthorized Storage Grade modificationsIn Grid Manager, go to Configuration > Storage Settings > Storage Grades. Verify that no unexpected modifications have been made to storage grades. Compare current configuration against any known-good baseline or backup.Affected if Storage Grades have been modified by users who should not have permission to make such changes.
-
Inspect Grid Topology for unexpected node information exposureIn Grid Manager, go to Support > Grid Topology. Compare the visible node names and IP addresses against documented baseline configuration. Check if this information is accessible to non-administrator users who should not normally see it.Affected if Non-administrator accounts can view Grid node names and IP addresses that should be restricted to administrative users.
A user is affected if their StorageGRID version falls within the vulnerable range (below 11.8.0.15 or between 11.9.0.0 and 11.9.0.7) AND there are non-administrator authenticated users present who can potentially access administrative functions.
Generated from the published advisory. Verify against your own configuration.
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 · scoped11.8.0.1511.9.0.8
Upgrade StorageGRID to version 11.8.0.15 or 11.9.0.8 or later. Prior to upgrade, verify current version and test upgrade in a non-production environment to ensure compatibility with existing configurations.
11.8.0.15 (for 11.8.x branch) or 11.9.0.8 (for 11.9.x branch)
- Identify current StorageGRID version by logging into the Grid Manager and navigating to Maintenance > System > Software Update, or by running: `sudo storagegrid --version`
- If running a version in the 11.8.x branch (before 11.8.0.15), plan upgrade to version 11.8.0.15
- If running a version in the 11.9.x branch (>= 11.9.0 and before 11.9.0.8), plan upgrade to version 11.9.0.8
- Follow NetApp's standard StorageGRID upgrade procedure: download the upgrade package from the NetApp Support Site, upload to Grid Manager, and run pre-check before initiating
- After upgrade, verify the new version is installed and confirm vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26517 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-26517 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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