| CVE ID | Severity | Package | Affected Version | Fixed Version | CVSS Score |
|---|---|---|---|---|---|
| CVE-2026-24049 | high | pkg:pypi/wheel@0.45.1 | >=0.40.0,<=0.46.1 | 0.46.2 | 7.1 |
Summary
DetailsThe vulnerability exists in how the unpack function handles file permissions after extraction. The code blindly trusts the filename from the archive header for the chmod operation, even though the extraction process itself might have sanitized the path.
PoCI have confirmed this exploit works against the unpack function imported from setuptools._vendor.wheel.cli.unpack. Prerequisites: pip install setuptools Step 1: Generate the Malicious Wheel (gen_poc.py)
Step 2: Run the Exploit (exploit.py)
result: ImpactAttackers can craft a malicious wheel file that, when unpacked, changes the permissions of critical system files (e.g., /etc/passwd, SSH keys, config files) to 777. This allows for Privilege Escalation or arbitrary code execution by modifying now-writable scripts. Recommended FixThe unpack function must not use zinfo.filename for post-extraction operations. It should use the sanitized path returned by wf.extract(). Suggested Patch:
Relevance: The relevance of CVE-2026-24049 depends on the specific usage of the python:3.10-slim image; if the application uses vulnerable components or libraries patched by this CVE, it could be critical in scenarios involving untrusted input or exposure to external networks. Without knowing the exact vulnerability details, it’s essential to assess if your application’s dependencies or environment are affected. Regular updates and security audits mitigate such risks. (Note: Relevance analysis is automatically generated and may require verification.) Package URL(s):
More Info (NVD): | |||||
| CVE-2023-5752 | medium | pkg:pypi/pip@23.0.1 | <23.3 | 23.3 | 6.8 |
| CVE-2025-8869 | medium | pkg:pypi/pip@23.0.1 | <=25.2 | 25.3 | 5.9 |
| CVE-2025-45582 | medium | tar | >=1.35+dfsg-3.1 | not fixed | 4.1 |
| CVE-2007-5686 | low | shadow | <=1:4.17.4-2 | not fixed | 3.1 |
| CVE-2018-20796 | low | glibc | <=2.41-12+deb13u1 | not fixed | 3.1 |
| CVE-2021-45346 | low | sqlite3 | <=3.46.1-7 | not fixed | 3.1 |
| CVE-2023-31437 | low | systemd | <=257.9-1~deb13u1 | not fixed | 3.1 |
| CVE-2023-31439 | low | systemd | <=257.9-1~deb13u1 | not fixed | 3.1 |
| CVE-2013-4392 | low | systemd | <=257.9-1~deb13u1 | not fixed | 3.1 |
Exploitation could lead to severe consequences, such as system compromise or data loss. Requires immediate attention.
Vulnerability could be exploited relatively easily and lead to significant impact. Requires prompt attention.
Exploitation is possible but might require specific conditions. Impact is moderate. Should be addressed in a timely manner.
Exploitation is difficult or impact is minimal. Address when convenient or as part of regular maintenance.
Severity is not determined, informational, or negligible. Review based on context.
Sliplane is a simple container hosting solution. It enables you to deploy your containers in the cloud within minutes and scale up as you grow.
CVE stands for Common Vulnerabilities and Exposures. It is a standardized identifier for known security vulnerabilities, allowing developers and organizations to track and address potential risks effectively. For more information, visit cve.mitre.org.
The CVE Scanner is a powerful tool that helps you identify known vulnerabilities in your Docker images. By scanning your images against a comprehensive database of Common Vulnerabilities and Exposures (CVEs), you can ensure that your applications are secure and up-to-date. For more details, checkout the NIST CVE Database.
The CVE Scanner analyzes your Docker images against a comprehensive database of known vulnerabilities. It uses Docker Scout under the hood to provide detailed insights into affected packages, severity levels, and available fixes, empowering you to take immediate action.
With the rise of supply chain attacks, ensuring the security of your applications has become more critical than ever. CVE scanning plays a vital role in identifying vulnerabilities that could be exploited by attackers, especially those introduced through dependencies and third-party components. Regularly scanning and securing your Docker images is essential to protect your applications from these evolving threats.
Patching your Docker images is a critical step in maintaining the security and stability of your applications. By regularly updating your images to include the latest security patches, you can address known vulnerabilities and reduce the risk of exploitation. This proactive approach ensures that your applications remain resilient against emerging threats and helps maintain compliance with security best practices.