LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22050: ONTAP versions 9.16.1 prior to 9.16.1P9 and 9.17.1 prior to 9.17.1P2 with snapshot locking enabled are susc...

ONTAP versions 9.16.1 prior to 9.16.1P9 and 9.17.1 prior to 9.17.1P2 with snapshot locking enabled are susceptible to a vulnerability which could allow a privileged remote attacker to set the snapshot expiry time to none.

MediumCVSS 6.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This NetApp ONTAP issue affects specific 9.16.1 and 9.17.1 releases when snapshot locking is enabled. A privileged remote user could change locked snapshot expiry to “none,” weakening retention controls. Business impact is mainly integrity and governance risk for protected snapshots, not broad system takeover based on the provided CVSS details.

Executive priority

Prioritize remediation for ONTAP systems using snapshot locking for compliance, ransomware resilience, or retention guarantees. The issue is not described as actively exploited, but it can undermine trusted snapshot retention if privileged access is misused or compromised.

Technical view

CVE-2026-22050 is a medium-severity ONTAP 9 vulnerability in versions 9.16.1 before 9.16.1P9 and 9.17.1 before 9.17.1P2 with snapshot locking enabled. CVSS 4.0 score is 6.9. The issue requires high privileges, network access, and no user interaction, with high impact to vulnerable-system integrity.

Likely exposure

Exposure appears limited to NetApp ONTAP 9 deployments on affected release branches where snapshot locking is enabled and privileged remote access exists. Systems outside those versions, or without snapshot locking enabled, are not identified as affected in the provided sources.

Exploitation context

The provided sources do not report active exploitation, and this CVE is not listed as KEV in the supplied data. Exploitation would require a privileged remote attacker, so compromised administrator credentials or misuse by a trusted privileged user is the main concern.

Researcher notes

Evidence is limited to the CVE record and NetApp advisory reference in the provided bundle. The affected condition is specific: ONTAP 9.16.1 before P9 and 9.17.1 before P2 with snapshot locking enabled. Avoid assuming impact on other ONTAP versions or NetApp products without vendor confirmation.

Mitigation direction

  • Upgrade ONTAP 9.16.1 systems to 9.16.1P9 or later.
  • Upgrade ONTAP 9.17.1 systems to 9.17.1P2 or later.
  • Review NetApp advisory NTAP-20260112-0001 for current vendor guidance.
  • Limit and monitor privileged remote access to ONTAP management interfaces.

Validation and detection

  • Inventory ONTAP clusters and confirm exact 9.16.1 or 9.17.1 patch levels.
  • Check whether snapshot locking is enabled on affected systems.
  • Review privileged account activity related to snapshot retention or expiry settings.
  • Confirm remediation by verifying patched ONTAP versions after upgrade.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-639: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-22050 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.9 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.9CVSS 4.0MediumCVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

6.9Medium
CVSS 4.0 vector shape for CVE-2026-22050Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
NETAPPONTAP 99.16.1, 9.17.1unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-639 · source CWE mapping

Authorization Bypass Through User-Controlled Key

Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.