dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2025-26470

MEDIUM · 6.7 CVSS v3.1 Published 2025-08-12
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 some Intel(R) Distribution for Python software installers before version 2025.1.0 may allow an authenticated user to potentially enable escalation of privilege via local 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 confidence

Intel Distribution for Python installers before version 2025.1.0 ship with incorrect default permissions that allow an authenticated local user to manipulate installer files or directories to achieve privilege escalation.

MitigationUpgrade Intel Distribution for Python to version 2025.1.0 or later to obtain corrected installer 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. Locate Intel Distribution for Python installer files
    Search common download directories (e.g., user Downloads folder, /tmp, C:\Users\*\Downloads on Windows, /home/*/Downloads on Linux) for Intel Distribution for Python installer files (typically named intel_python*.exe, intel_python*.msi, or similar)
    Affected if Installer files exist from versions before 2025.1.0
  2. Identify installed Intel Distribution for Python version
    Check the installed product version. On Windows, look in Programs and Features or check the installation directory for version metadata. On Linux, check /opt/intel/ or similar installation paths for version files. Use command: 'pip show intel-scipy' or search for intel-related packages with 'pip list | grep intel'
    Affected if Installed version is found to be earlier than 2025.1.0
  3. Examine installer file permissions
    For installer files found in step 1, check file/directory permissions. On Windows, right-click the file > Properties > Security tab. On Linux, run 'ls -la <installer_path>' to view permissions (look for world-writable or group-writable permissions)
    Affected if Installer files or their parent directories grant write access to non-privileged users (permissions show 'Everyone', 'Users', or similar broad access with Write permissions)
  4. Check installation directory permissions
    Inspect the directory where Intel Distribution for Python is installed. Look for directories that may have been created or modified by the installer. Verify that standard users cannot modify installer-related files or directories
    Affected if Installation directories or files are writable by authenticated local users who should not have elevated access

A system is affected if Intel Distribution for Python installer files or installation directories from versions before 2025.1.0 exist with overly permissive file access controls that allow standard users to modify installer artifacts.

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 Distribution for Python to version 2025.1.0 or later to obtain corrected installer permissions.

Recommended fix High confidence

Intel Distribution for Python 2025.1.0 or later

  1. Identify currently installed Intel Distribution for Python version using 'pip show intel-sys' or checking installation directory
  2. Download Intel Distribution for Python version 2025.1.0 or later from the official Intel website or trusted distribution channel
  3. Uninstall the vulnerable older version using 'pip uninstall intel-sys' or the appropriate package manager
  4. Install the fixed version (2025.1.0 or later) using the downloaded installer
  5. Verify the installation completed successfully and confirm the new version is installed
  6. Ensure the installed files have appropriate permissions set (restrictive permissions on sensitive installer files)
Caveat Review release notes for any API or compatibility changes between your current version and 2025.1.0

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
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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 locally
dbcve dependency scanner

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