CVE-2021-26995
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 · uneditedE-Series SANtricity OS Controller Software 11.x versions prior to 11.70.1 are susceptible to a vulnerability which when successfully exploited could allow privileged attackers to execute arbitrary code.
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 confidenceE-Series SANtricity OS Controller Software versions 11.x prior to 11.70.1 contains a vulnerability that allows authenticated privileged attackers to execute arbitrary code on the controller, likely through improper input validation or privilege escalation in the controller's web management interface.
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.0.0, < 11.70.1CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed SANtricity OS versionAccess the SANtricity System Manager or use the SANtricity CLI command to retrieve the controller OS version. Navigate to the About or Support section in the web interface, or run 'show storageArray' in the CLI.Affected if Installed version is 11.0.0 or later but below 11.70.1
-
Confirm web management interface is enabledIn SANtricity System Manager, verify that the web-based management interface (Controller | Setup | Enable/Disable Management Interfaces) is active. This is typically enabled by default for administrative access.Affected if Web management interface is accessible and enabled on the controller
-
Verify authentication configurationCheck the SANtricity user role assignments under Access Management to confirm which accounts have "Administrator" or "Super" privileges, as the vulnerability requires authenticated privileged access.Affected if Any user account with privileged (Administrator/Super) rights exists in the system
-
Review controller audit logs for suspicious privileged activityAccess the SANtricity audit logs under Support | Audit Log and look for unexpected commands, API calls, or configuration changes executed by privileged users, particularly those originating from unexpected sources or at unusual times.Affected if Audit logs show unauthorized or suspicious privileged commands that were not initiated by legitimate administrators
Your environment is affected if the SANtricity OS controller version is 11.0.0 through 11.70.0 and the web management interface with privileged user accounts is accessible.
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.70.1
Upgrade SANtricity OS Controller Software to version 11.70.1 or later to remediate this vulnerability.
11.70.1
- Log into the NetApp Support Site and download the SANtricity OS 11.70.1 (or later) firmware package for your specific E-Series storage system
- Review the SANtricity OS Controller Software 11.70.1 release notes for any special instructions or prerequisites
- Schedule a maintenance window as the controller upgrade may cause brief I/O disruption
- Back up the storage array's configuration using SANtricity System Manager
- Upload the new firmware through SANtricity System Manager: Navigate to Hardware > firmware upgrade, select the downloaded firmware file, and initiate the upgrade
- Monitor the upgrade progress and verify all controllers are running the new version post-upgrade
- Verify normal array operation and data access after the upgrade completes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-26995 — 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-2021-26995 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