CVE-2025-46602
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 · uneditedDell SupportAssist OS Recovery, versions prior to 5.5.15.0, contain an Insertion of Sensitive Information into Externally-Accessible File or Directory vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to Information exposure.
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 confidenceDell SupportAssist OS Recovery versions prior to 5.5.15.0 contain a vulnerability where sensitive information is written to an externally-accessible file or directory. A low-privileged local attacker can access this information due to improper file or directory permissions or insecure storage location.
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< 5.5.15.0CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Check if Dell SupportAssist OS Recovery is installedLook for Dell SupportAssist OS Recovery in the list of installed programs via Windows Settings > Apps & features, or check the Program Files directory for SupportAssist folders.Affected if Dell SupportAssist OS Recovery is present on the system
-
Determine the installed versionOpen the SupportAssist application and navigate to About or Settings > Support Information to view the version number. Alternatively, check the version in Add/Remove Programs or the executable file properties.Affected if The installed version is lower than 5.5.15.0
-
Locate files containing sensitive informationSearch the SupportAssist installation directory and associated data folders (commonly in Program Files/Dell/SupportAssist or %ProgramData%/Dell) for log files, configuration files, or data files that may contain sensitive information such as credentials, system details, or personal data.Affected if Sensitive data files exist in SupportAssist directories
-
Check file and directory permissionsRight-click on the identified sensitive files and folders, select Properties, then Security. Verify which user accounts have Read or Write access. Use icacls or Get-Acl in PowerShell to inspect permissions more thoroughly.Affected if Low-privileged standard users or the Everyone group have Read access to files containing sensitive information
-
Determine if files are externally accessibleCheck if the SupportAssist data directories are located in shared folders, network-accessible locations, or directories with weak permissions that could be accessed by other local users or external attackers.Affected if Sensitive files are accessible from low-privileged local accounts or external locations
A system is affected if Dell SupportAssist OS Recovery version lower than 5.5.15.0 is installed and sensitive files or directories are accessible to low-privileged users due to improper permissions.
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 · scoped5.5.15.0
Update Dell SupportAssist OS Recovery to version 5.5.15.0 or later to obtain the vendor patch addressing this vulnerability.
5.5.15.0
- Check the current version of Dell SupportAssist OS Recovery installed on the system
- Navigate to www.dell.com/support or the Dell SupportAssist download page
- Locate the Dell SupportAssist OS Recovery download for version 5.5.15.0 or later
- Download the installer from the official Dell support website
- Run the installer as an administrator to apply the update
- Verify the installation completed successfully by checking the updated version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46602 — 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-2025-46602 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