dbcve.org
SnapcenterApplication · Netapp

CVE-2025-26512

CRITICAL · 9.9 CVSS v3.1 Published 2025-03-24
Fix available
A fix is available. Upgrade to 6.0.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
SnapCenter versions prior to 6.0.1P1 and 6.1P1 are susceptible to a vulnerability which may allow an authenticated SnapCenter Server user to become an admin user on a remote system where a SnapCenter plug-in has been installed.

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 confidence

This is a privilege escalation vulnerability in SnapCenter Server where an authenticated user can elevate their privileges to become an admin user on remote systems where SnapCenter plug-ins are installed. The vulnerability allows lateral movement from the SnapCenter Server to managed plug-in hosts, bypassing normal authorization controls.

MitigationUpgrade SnapCenter to version 6.0.1P1 or 6.1P1 or later. Additionally, review user access logs on affected SnapCenter Server and remote plug-in systems for signs of unauthorized privilege escalation.

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
SnapcenterApplication
Affected:< 6.0.1= 6.0.1= 6.1

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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

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. Confirm SnapCenter installation
    Check if SnapCenter Server is installed by looking for the SnapCenter service or installation directory. On Windows, check Services for 'SnapCenter Server' or look in C:\Program Files\NetApp\SnapCenter\
    Affected if SnapCenter Server is not installed on the system
  2. Identify installed SnapCenter version
    Run 'Get-PSSnapin -Name NetApp.SnapCenter' to get version info, or check the SnapCenter GUI under the 'About' menu, or look in the installation directory for version.txt
    Affected if Version cannot be determined or is not visible
  3. Compare version against affected ranges
    Compare your installed SnapCenter version to the affected ranges: < 6.0.1, = 6.0.1, or = 6.1. If running 6.0.1, verify if patch 6.0.1P1 or later is applied by checking the installed build number
    Affected if Installed version is 6.0.1 (without P1 or later patch), 6.1, or any version below 6.0.1
  4. Check for remote plug-in installations
    In SnapCenter GUI, navigate to 'Hosts' or 'Plug-ins' section to see which remote hosts have SnapCenter plug-ins installed and configured for communication with the SnapCenter Server
    Affected if Remote hosts have SnapCenter plug-ins installed and are managed by this SnapCenter Server
  5. Verify plug-in communication configuration
    In SnapCenter, go to Settings > Global Settings > Plug-in Settings to review how plug-ins communicate with the server and what authentication is in use
    Affected if Plug-ins are configured to communicate with the SnapCenter Server using default or unvalidated credentials

You are affected if SnapCenter Server version is 6.0.1, 6.1, or any version below 6.0.1, and you have remote hosts with SnapCenter plug-ins installed and managed by this server.

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 6.0.1 or later
Fixed in 6.0.1
Interim mitigation

Upgrade SnapCenter to version 6.0.1P1 or 6.1P1 or later. Additionally, review user access logs on affected SnapCenter Server and remote plug-in systems for signs of unauthorized privilege escalation.

Recommended fix High confidence

6.0.1P1 or 6.1P1 (or later stable releases in respective branches)

  1. Identify current SnapCenter version from the SnapCenter Dashboard or using Get-SmVersion cmdlet
  2. If version is < 6.0.1, upgrade to 6.0.1P1 or later stable release
  3. If version is exactly 6.0.1, upgrade to 6.0.1P1 or later stable release
  4. If version is exactly 6.1, upgrade to 6.1P1 or later stable release
  5. Download the appropriate patch from the NetApp support site (support.netapp.com) using valid support credentials
  6. Review NetApp SnapCenter upgrade documentation before proceeding
  7. Backup the SnapCenter repository and configuration before upgrade
  8. Execute upgrade during a planned maintenance window
Caveat Review NetApp upgrade documentation for any compatibility requirements with host plug-ins, databases, and dependent services before upgrading

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

Fix this in Snapcenter Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-26512 — 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-26512 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