dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-22048

HIGH · 7.1 CVSS v3.1 Published 2026-02-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
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
StorageGRID (formerly StorageGRID Webscale) versions prior to 11.9.0.12 and 12.0.0.4 with Single Sign-on enabled and configured to use Microsoft Entra ID (formerly Azure AD) as an IdP are susceptible to a Server-Side Request Forgery (SSRF) vulnerability. Successful exploit could allow an authenticated attacker with low privileges to delete configuration data or deny access to some resources.

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

StorageGRID versions prior to 11.9.0.12 and 12.0.0.4 contain an SSRF vulnerability in the Single Sign-on component when Microsoft Entra ID (Azure AD) is configured as the identity provider. An authenticated attacker with low privileges can craft malicious requests through the StorageGRID system to delete configuration data or cause denial of access to resources.

MitigationUpgrade StorageGRID to version 11.9.0.12 or 12.0.0.4 or later. If immediate patching is not feasible, consider disabling SSO or temporarily switching to an alternative IdP until the upgrade can be completed.

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

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
Unchanged
Confidentiality
None
Integrity
Low
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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. Identify StorageGRID version
    Access the StorageGRID Grid Manager or use the `sudo storagegrid --version` command (or check the support page in the management interface) to determine the installed version
    Affected if The installed version is prior to 11.9.0.12 or 12.0.0.4
  2. Verify SSO is enabled
    Log into the Grid Manager and navigate to Identity Provider configuration (Access Control > Identity Providers) or check the SSO settings in the management interface
    Affected if Single Sign-on (SSO) is currently enabled on the system
  3. Confirm Microsoft Entra ID (Azure AD) is the configured IdP
    In the Identity Provider settings, examine the configured identity provider type - look for Microsoft Entra ID (formerly Azure AD) or Azure Active Directory as the selected IdP
    Affected if Microsoft Entra ID/Azure AD is selected as the identity provider for SSO
  4. Check for low-privilege authenticated users
    Review user accounts in the Grid Manager (Access Control > Users) and identify any users with limited or non-admin privileges who have SSO access
    Affected if There are authenticated users with low privileges who can access the system via SSO

The system is affected if it runs StorageGRID version below 11.9.0.12 or 12.0.0.4 AND has SSO enabled with Microsoft Entra ID/Azure AD as the identity provider, allowing a low-privilege authenticated attacker to exploit the SSRF vulnerability.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade StorageGRID to version 11.9.0.12 or 12.0.0.4 or later. If immediate patching is not feasible, consider disabling SSO or temporarily switching to an alternative IdP until the upgrade can be completed.

Recommended fix High confidence

StorageGRID 11.9.0.12 (for 11.x branches) or StorageGRID 12.0.0.4 (for 12.x branches)

  1. 1. Identify current StorageGRID version by logging into the Grid Manager and navigating to 'About' or checking the version via the API
  2. 2. Determine which upgrade path applies: versions 11.x should upgrade to 11.9.0.12, versions 12.x should upgrade to 12.0.0.4
  3. 3. Review NetApp StorageGRID upgrade documentation and ensure prerequisites are met before upgrading
  4. 4. Create a complete backup of the StorageGRID configuration
  5. 5. Perform the upgrade following NetApp's recommended upgrade procedure for your current version
  6. 6. After upgrade, verify that Single Sign-On configuration with Microsoft Entra ID still functions correctly
  7. 7. Confirm the fix by checking that the system is no longer vulnerable to SSRF via the Entra ID integration
Caveat Review NetApp upgrade documentation for version-specific considerations; ensure backup and rollback procedures are in place before proceeding

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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 locally
dbcve dependency scanner

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