dbcve.org
Unity Operating EnvironmentApplication · Dell

CVE-2026-22277

HIGH · 7.8 CVSS v3.1 Published 2026-01-30
Fix available
A fix is available. Upgrade to 5.5.3.0 or later.
See remediation →
80/100
Remediation priority · High
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
Dell UnityVSA, version(s) 5.4 and prior, contain(s) an Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to arbitrary command execution with root privileges.

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

Dell UnityVSA versions 5.4 and prior contain an OS command injection vulnerability (CWE-78) where improper neutralization of special elements in user input allows a low-privileged local attacker to execute arbitrary operating system commands with root privileges.

MitigationUpgrade Dell UnityVSA to a patched version. Additionally, implement proper input validation and sanitization for all user-controlled data passed to OS command execution functions, and restrict local access to trusted personnel.

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
Unity Operating EnvironmentApplication
Affected:< 5.5.3.0

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Dell Unity product variant
    Run 'dmidecode -s system-product-name' or check the system documentation to confirm whether the system is Dell UnityVSA or Dell Unity Operating Environment (Unity OE)
    Affected if The product is Dell UnityVSA or Dell Unity OE and the variant cannot be determined
  2. Determine the installed version of Dell UnityVSA
    Access the management interface or CLI and run the command to display the system version (typically 'esxcli system version get' for VSA or check the About page in Unisphere)
    Affected if The version is 5.4 or any version prior to 5.4
  3. Determine the installed version of Dell Unity Operating Environment
    Access Unisphere or the CLI and retrieve the OE version (check 'nas_version' or the system information panel in the management GUI)
    Affected if The version is below 5.5.3.0
  4. Verify if low-privileged local user accounts exist
    Check /etc/passwd or use 'getent passwd' to list local user accounts, focusing on non-root users with shell access
    Affected if Low-privileged local user accounts with shell or API access are present on the system
  5. Confirm the management interface is accessible
    Attempt to reach the Unisphere web interface or verify the CLI is accessible via SSH/telnet on the management ports
    Affected if The management interface or CLI is reachable by the local attacker

A system is affected if it runs Dell UnityVSA version 5.4 or prior, or Dell Unity Operating Environment version below 5.5.3.0, and allows low-privileged local users to access the system or its management interface.

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

Upgrade Dell UnityVSA to a patched version. Additionally, implement proper input validation and sanitization for all user-controlled data passed to OS command execution functions, and restrict local access to trusted personnel.

Recommended fix Moderate confidence

Dell UnityVSA 5.5.3.0 or later

  1. 1. Identify the current Dell UnityVSA version by accessing the system management interface or using the Unity CLI
  2. 2. Download Dell UnityVSA version 5.5.3.0 or later from the Dell Support website (support.dell.com)
  3. 3. Create a complete backup of the current UnityVSA configuration and data
  4. 4. Schedule a maintenance window as the upgrade may require system downtime
  5. 5. Follow Dell's official upgrade documentation to apply the update
  6. 6. After upgrade, verify the system is running version 5.5.3.0 or later
  7. 7. Confirm that the OS command injection vulnerability is no longer present
Caveat Review Dell UnityVSA 5.5.x release notes for any configuration or feature changes between your current version and 5.5.3.0

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

Fix this in Unity Operating Environment Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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