dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2026-0432

HIGH · 8.5 CVSS v4.0 Published 2026-05-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/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
Incorrect default permissions in the installation directory for the AMD chipset driver could allow an attacker to achieve privilege escalation resulting in arbitrary code execution.

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 confidence

This is a local privilege escalation vulnerability in AMD chipset drivers where the installation directory has overly permissive file system permissions (likely world-writable or allowing low-privileged user modification). An attacker with low-privileged access can replace or modify executables, DLLs, or configuration files in the installation path that are subsequently executed by higher-privileged processes (services, scheduled tasks, or system components), achieving arbitrary code execution with elevated privileges.

MitigationRestrict permissions on the AMD chipset driver installation directory to deny write access for non-privileged users; only SYSTEM, Administrators, and the installation owner should have write/modify permissions. After correcting ACLs, verify the driver functionality remains intact.

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
Local
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Locate AMD chipset driver installation directory
    Search for common AMD driver installation paths such as C:\Program Files\AMD\, C:\Windows\System32\DriverStore\FileRepository\ (filter for amd* folders), or C:\Program Files\Common Files\AMD\. Use 'dir C:\Program Files\AMD /s /b' or 'Get-ChildItem -Path C:\ -Recurse -Directory -ErrorAction SilentlyContinue | Where-Object {$_.Name -like "*AMD*"}' in PowerShell.
    Affected if The AMD driver directory exists on the system.
  2. Check permissions on the AMD driver directory
    Right-click the identified AMD driver folder, go to Properties > Security tab, or run 'icacls "<AMD_driver_path>"' from an elevated command prompt to view all granted permissions.
    Affected if Users, Everyone, or Authenticated Users groups have Write or Full Control permissions.
  3. Verify low-privilege user write access
    From a standard (non-admin) user account, attempt to create a test file in the AMD driver directory using 'echo test > "<AMD_driver_path>\test_write.txt"' or attempt to delete/modify an existing file.
    Affected if The operation succeeds, confirming the directory is world-writable or modifiable by low-privileged users.
  4. Inspect driver files, DLLs, and config for modification access
    List contents of the AMD driver directory with 'dir /a' or 'Get-ChildItem -Force' and verify file permissions with 'icacls "<file_path>"' on .sys, .dll, and .ini/.cfg files.
    Affected if Driver files (.sys), dynamic-link libraries (.dll), or configuration files (.ini, .cfg, .xml) are writable by non-admin users.

If the AMD chipset driver installation directory and its contents grant Write or Full Control permissions to standard users, Authenticated Users, or Everyone, the system is vulnerable to privilege escalation via driver file modification.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict permissions on the AMD chipset driver installation directory to deny write access for non-privileged users; only SYSTEM, Administrators, and the installation owner should have write/modify permissions. After correcting ACLs, verify the driver functionality remains intact.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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