Supportassist Os RecoveryApplication · Dell

CVE-2022-26865

MEDIUM · 6.8 CVSS v3.1 Published 2022-05-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
No privileges 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 Support Assist OS Recovery versions before 5.5.2 contain an Authentication Bypass vulnerability. An unauthenticated attacker with physical access to the system may exploit this vulnerability by bypassing OS Recovery authentication in order to run arbitrary code on the system as Administrator.

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 Support Assist OS Recovery versions before 5.5.2 contain an authentication bypass vulnerability that allows an unauthenticated attacker with physical access to bypass OS Recovery authentication and execute arbitrary code with Administrator privileges.

MitigationUpdate Dell Support Assist OS Recovery to version 5.5.2 or later. Physical security controls should be enforced to prevent unauthorized access to the system.

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
Supportassist Os RecoveryApplication
Affected:= 5.5.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
Physical
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:P/AC:L/PR:N/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. Verify Dell Support Assist OS Recovery is installed
    Check for Dell Support Assist OS Recovery software on the system through Programs and Features (Windows) or package manager (Linux), or look for its installation directory under Program Files or Dell directories
    Affected if The software is present on the system
  2. Identify the installed version of Dell Support Assist OS Recovery
    Open the application or check its properties/About section to find the exact version number, or look in the Windows Registry under HKLM\SOFTWARE\Dell\SupportAssist\OSRecovery for the Version value
    Affected if The version displayed is 5.5.1 or any version earlier than 5.5.2
  3. Confirm the OS Recovery feature is enabled
    Access the Dell Support Assist OS Recovery environment (typically accessed during boot via F12 or a dedicated recovery partition) and verify the recovery functionality is accessible
    Affected if OS Recovery is accessible and the version is 5.5.1 or earlier

If Dell Support Assist OS Recovery version 5.5.1 is installed (or any version before 5.5.2), the system is affected by this authentication bypass vulnerability when physical access to the OS Recovery environment is possible.

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

Update Dell Support Assist OS Recovery to version 5.5.2 or later. Physical security controls should be enforced to prevent unauthorized access to the system.

Recommended fix High confidence

5.5.2

  1. Identify the current version of Dell Support Assist OS Recovery installed on the system
  2. Navigate to Dell's official support website (www.dell.com) and locate the Support Assist OS Recovery download page
  3. Download the version 5.5.2 update or latest available version from Dell's official support page
  4. Verify the downloaded file integrity using checksums if provided by Dell
  5. Execute the installer with Administrator privileges
  6. Follow the on-screen prompts to complete the installation
  7. Restart the system if prompted
  8. Confirm the installed version is 5.5.2 or later

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

Fix this in Supportassist Os Recovery Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-26865 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-26865 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