| CVE ID | Severity | Package | Affected Version | Fixed Version | CVSS Score |
|---|---|---|---|---|---|
| CVE-2026-115905 | critical | pkg:cargo/zip@8.6.0 | <=9.0.4 | 9.0.5 | 10.0 |
SummaryA critical architectural parser differential exists in the This discrepancy enables ZIP archives to appear to have different file paths and contents according to which tool is reading them. DetailsArchitectural Root CauseIn the PKWARE ZIP archive format, every file entry is defined in two distinct locations:
In
Threat Scenario & Severity Justification (10.0 / 9.9 Critical)
Proof of ConceptThe following automated integration test reproducibly demonstrates the complete CVSS 10.0 / 9.9 exploit chain (Security Gateway Evasion -> Arbitrary File Overwrite -> RCE & DoS) against
Verified Test Execution Output
ImpactAn attacker can construct a crafted archive whose Central Directory displays a benign filename (doc_report.pdf) that is inspected and approved by upstream security gateways (antivirus scanners, mail filters, upload firewalls), while automated backend ingestion pipelines or microservices using ZipStreamReader extract an arbitrary or malicious file (overwriting e.g. cron_worker.sh or critical system binaries). Because an adversary can overwrite existing files on disk, this vulnerability leads to Security Control Bypass, Arbitrary File Overwrite, Complete Denial of Service, and Remote Code Execution (RCE) in situations where a tool relying on the central directory trusts a tool that relied on the local file headers or vice-versa. Who is Impacted:
Package URL(s):
More Info (NVD): | |||||
| CVE-2026-56857 | critical | pkg:golang/stdlib@1.26.6 | <1.26.9 | 1.26.9 | 9.8 |
| CVE-2026-78663 | critical | net | <0.60.0 | 0.60.0 | 9.1 |
| GHSA-4684-h2q9-2vcp | critical | pkg:cargo/zip@8.6.0 | <9.0.0 | 9.0.0 | 9.1 |
| GHSA-wq5f-xc86-pv6w | high | pkg:npm/sharp@0.35.4 | <0.35.5 | 0.35.5 | 8.9 |
| CVE-2026-116693 | high | pkg:npm/dd-trace@5.100.0 | >=2.0.0,<5.131.1 | 5.131.1 | 8.7 |
| CVE-2026-85393 | high | pkg:npm/node-forge@1.4.0 | <=1.4.0 | not fixed | 8.7 |
| RUSTSEC-2026-0245 | high | pkg:cargo/sevenz-rust@0.6.1 | >=0.0.0-0 | not fixed | 8.3 |
| CVE-2023-54404 | high | pkg:npm/zod@3.23.8 | <4.6.6 | 4.6.6 | 8.2 |
| CVE-2026-111755 | high | pkg:npm/follow-redirects@1.16.0 | >=1.16.0,<1.16.1 | 1.16.1 | 8.2 |
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 cloud platform that makes deploying and scaling your apps simple. Launch in minutes and grow as you go, containers included.
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.
Try out Sliplane - a simple Docker hosting solution. It provides you with the tools to deploy, manage and scale your containerized applications.