CVE-2026-24049: wheel Allows Arbitrary File Permission Modification via Path Traversal
wheel is a command line tool for manipulating Python wheel files, as defined in PEP 427. In versions 0.40.0 through 0.46.1, the unpack function is vulnerable to file permission modification through mishandling of file permissions after extraction. The logic blindly trusts the filename from the archive header for the chmod operation, even though the extraction process itself might have sanitized the path. Attackers can craft a malicious wheel file that, when unpacked, changes the permissions of critical system files (e.g., /etc/passwd, SSH keys, config files), allowing for Privilege Escalation or arbitrary code execution by modifying now-writable scripts. This issue has been fixed in version 0.46.2.
Security readout for executives and security teams
Plain-English summary
Python wheel versions 0.40.0 through 0.46.1 can mishandle file permissions when unpacking a malicious wheel archive. A user or automated process that unpacks such a file could unintentionally make sensitive files writable, creating a path to privilege escalation or code execution.
Executive priority
Prioritize remediation in build and developer environments, especially where automation handles third-party Python packages. This is not described as remotely exploitable from the supplied sources, but compromise of build systems can have high downstream impact.
Technical view
The unpack function trusts archive header filenames during chmod after extraction. Because extraction may sanitize paths differently than the permission-change step, crafted paths can cause permission changes outside the intended destination. CVSS is 7.1, with local attack vector and required user interaction. Fixed upstream in wheel 0.46.2.
Likely exposure
Exposure is most likely in developer workstations, CI systems, build images, packaging automation, or security analysis workflows that unpack Python wheel files using affected wheel versions. Internet-facing services are not directly implicated by the supplied sources unless they process untrusted wheels locally.
Exploitation context
The supplied data does not show CISA KEV listing or active exploitation. Exploitation requires a malicious wheel file to be unpacked by an affected tool version. The business risk is higher where builds run with elevated permissions or access sensitive files.
Researcher notes
Focus validation on the unpack code path, package provenance, runtime privilege, and filesystem access. The sources identify the vulnerable version range and fixed release, but do not provide evidence of active exploitation or a universal distro-level fix beyond referenced vendor advisories.
Mitigation direction
Upgrade Python wheel to version 0.46.2 or later.
Apply relevant Red Hat errata where wheel is supplied by Red Hat packages.
Avoid unpacking untrusted wheel files on sensitive hosts.
Run wheel inspection or unpacking in isolated, low-privilege environments.
Check vendor guidance for distribution-specific package status.
Validation and detection
Inventory installed wheel versions across workstations, CI runners, and build images.
Flag versions greater than or equal to 0.40.0 and less than 0.46.2.
Review pipelines for workflows that unpack externally supplied wheel files.
Confirm patched vendor packages are installed where OS packages provide wheel.
Validate build jobs do not run wheel unpacking with unnecessary privileges.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
CWE-732: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.