dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2025-22849

MEDIUM · 6.7 CVSS v3.1 Published 2026-02-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated

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 for the Intel(R) Optane(TM) PMem management software before versions CR_MGMT_01.00.00.3584, CR_MGMT_02.00.00.4052, CR_MGMT_03.00.00.0538 within Ring 3: User Applications may allow an escalation of privilege. Unprivileged 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 confidence

Intel Optane PMem management software contains incorrect default permissions in Ring 3 (user applications) that could allow an authenticated unprivileged user to escalate privileges to higher levels. The attack requires local access, active user interaction, and high complexity, making exploitation difficult but possible.

MitigationUpgrade Intel Optane PMem management software to version CR_MGMT_01.00.00.3584, CR_MGMT_02.00.00.4052, or CR_MGMT_03.00.00.0538 (depending on the software branch) to remediate the improper permissions.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Intel Optane PMem management software is installed
    Look for Intel Optane PMem management software in the system installed programs list. On Windows, check Add/Remove Programs or the program directory. On Linux, check for packages related to optane or persistent memory management.
    Affected if The software is present on the system
  2. Identify the installed version number
    Open the management software or check its executable properties for the version. Common locations include the program installation directory or use system inventory tools to query installed software versions.
    Affected if The version cannot be determined or is older than the fixed releases
  3. Compare installed version to fixed releases
    Compare your installed version against the fixed versions: CR_MGMT_01.00.00.3584, CR_MGMT_02.00.00.4052, or CR_MGMT_03.00.00.0538 depending on your software branch.
    Affected if The installed version is lower than the corresponding fixed version for your branch
  4. Inspect file permissions on management software binaries
    Check the file system permissions on the Intel Optane PMem management software executables and configuration files. Verify whether user-mode applications (Ring 3) have excessive write or execute permissions that should be restricted to administrator or system accounts.
    Affected if Non-privileged users have permissions that should be restricted to higher privilege levels

If the Intel Optane PMem management software is installed and the version is below the fixed releases, the environment is vulnerable to incorrect default permissions that could enable privilege escalation.

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

Upgrade Intel Optane PMem management software to version CR_MGMT_01.00.00.3584, CR_MGMT_02.00.00.4052, or CR_MGMT_03.00.00.0538 (depending on the software branch) to remediate the improper permissions.

Recommended fix High confidence

Intel Optane PMem management software: CR_MGMT_01.00.00.3584 (or later for 01.x track), CR_MGMT_02.00.00.4052 (or later for 02.x track), CR_MGMT_03.00.00.0538 (or later for 03.x track)

  1. Identify the current version of Intel(R) Optane(TM) PMem management software installed on the system
  2. Determine which release track (CR_MGMT_01.x, CR_MGMT_02.x, or CR_MGMT_03.x) is currently in use
  3. Download the appropriate fixed version from Intel's official support website or through your existing Intel software distribution channel
  4. For CR_MGMT_01.x track: upgrade to version CR_MGMT_01.00.00.3584 or later
  5. For CR_MGMT_02.x track: upgrade to version CR_MGMT_02.00.00.4052 or later
  6. For CR_MGMT_03.x track: upgrade to version CR_MGMT_03.00.00.0538 or later
  7. Verify the installation was successful and confirm the new version number
  8. Restart any dependent services if required by the upgrade

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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