CVE-2025-36522
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 · uneditedIncorrect default permissions for some Intel(R) Chipset Software before version 10.1.20266.8668 or later. within Ring 3: User Applications may allow an escalation of privilege. System software adversary with an authenticated user combined with a high complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are present without special internal knowledge and requires active user interaction. The potential vulnerability may impact the confidentiality (high), integrity (high) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.
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 confidenceIntel Chipset Software contains incorrect default permissions in Ring 3 (user-mode applications) that could allow an authenticated local user to escalate privileges through a high-complexity attack requiring active user interaction.
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
- High
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/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.
-
Identify Intel Chipset Software installationOpen Windows Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like "*Intel*Chipset*"}' in PowerShell to list installed Intel chipset-related software.Affected if Intel Chipset Software or related Intel chipset drivers are present in the installed programs list
-
Locate Intel Chipset driver versionOpen Device Manager, expand 'System devices' or 'Intel(R) Chipset' entries, right-click each Intel chipset device, select Properties, and view the Driver version field. Alternatively, check the file version of chipset driver files in C:\Windows\System32\drivers\ (typically starting with 'intelppm' or 'intel')Affected if A driver file with name starting with 'intelppm' or similar Intel chipset driver is found with a version number
-
Compare installed version against fixed releaseNote the exact version number found (from Program Details or Driver Version) and compare numerically to the fixed version 10.1.20266.8668. Ensure all four version segments are compared.Affected if The installed version is lower than 10.1.20266.8668 (for example, 10.1.x.x versions below 10.1.20266, or any earlier version family)
-
Check for Intel Management Engine componentsOpen Intel Driver & Support Assistant, or check Programs and Features for 'Intel(R) Management Engine Components' or 'Intel Chipset Software', and note the detailed version number shown in the installation properties.Affected if Intel Management Engine or Chipset Software components are installed with a version earlier than 10.1.20266.8668
If Intel Chipset Software or related Intel chipset/ME drivers are installed with a version earlier than 10.1.20266.8668, the environment is affected by this vulnerability.
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.
From vendor dataUpdate Intel Chipset Software to version 10.1.20266.8668 or later to remediate the incorrect default permissions vulnerability.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36522 — 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-36522 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