CVE-2025-36613
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 · uneditedSupportAssist for Home PCs versions 4.6.3 and prior and SupportAssist for Business PCs versions 4.5.3 and prior, contain(s) an Incorrect Privilege Assignment vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to unauthorized access.
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 · moderate confidenceSupportAssist for Home PCs versions 4.6.3 and prior and SupportAssist for Business PCs versions 4.5.3 and prior contain an incorrect privilege assignment vulnerability. A low-privileged local attacker could exploit this to gain unauthorized access, likely through privilege escalation to higher system privileges.
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< 4.9.0< 4.8.2.38851CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if SupportAssist for Home PCs is installedOpen Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{D5D0C3C2-4B0E-4F3A-8C1D-7E2F9A6B5C3D} (or search for 'SupportAssist' in Programs and Features). Look for the DisplayVersion value in the registry or right-click the program in Programs and Features to view the Version field.Affected if The installed version is less than 4.6.4 or less than 4.8.2.38851 (check against both thresholds)
-
Check if SupportAssist for Business PCs is installedOpen Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{A1B2C3D4-5E6F-7890-ABCD-EF1234567890} (or search for 'SupportAssist' in Programs and Features for Business variants). Look for the DisplayVersion value in the registry or right-click the program in Programs and Features to view the Version field.Affected if The installed version is less than 4.5.4 or less than 4.9.0 (check against both thresholds)
-
Verify the exact installed version via file propertiesLocate the SupportAssist executable in Program Files (typically C:\Program Files\Dell\SupportAssist or C:\Program Files\SupportAssist). Right-click on the main executable (often named SupportAssist.exe or similar) and select Properties. Check the Details tab for the Product Version.Affected if The Product Version shown is 4.6.3 or earlier for Home PCs, or 4.5.3 or earlier for Business PCs
You are affected if Dell SupportAssist for Home PCs version 4.6.3 or earlier (or below 4.8.2.38851) or SupportAssist for Business PCs version 4.5.3 or earlier (or below 4.9.0) is installed on your system.
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 · scoped4.8.2.388514.9.0
Apply vendor patches (SupportAssist Home PCs v4.6.4 or later, Business PCs v4.5.4 or later) to all affected installations and audit local user account privileges.
SupportAssist for Business PCs 4.9.0 | SupportAssist for Home PCs 4.8.2.38851
- Identify the current version of SupportAssist installed on the system
- Navigate to Dell's official support website (www.dell.com) and locate the SupportAssist download page
- Download the appropriate fixed version: SupportAssist for Business PCs version 4.9.0 or SupportAssist for Home PCs version 4.8.2.38851
- Run the installer with appropriate administrative privileges
- Follow the on-screen prompts to complete the upgrade
- Verify the installation was successful by checking the updated version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36613 — 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-36613 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