CVE Scan for node:lts-trixie-slim
Docker image vulnerability scanner
33 Known Vulnerabilities in this Docker Image
| CVE ID | Severity | Package | Affected Version | Fixed Version | CVSS Score |
|---|---|---|---|---|---|
| CVE-2026-12087 | critical | perl | >0 | not fixed | 9.1 |
Socket versions before 2.041 for Perl have an out-of-bounds heap read. In Socket.xs, pack_ip_mreq_source() checks the length of its source argument before the argument is read, so the check tests the byte length carried over from the preceding multiaddr argument instead. Both addresses occupy a 4-byte field, so a valid multiaddr lets a source of any length pass the check, and the source is then copied into the 4-byte imr_sourceaddr field with a fixed-size copy. A source shorter than 4 bytes is not rejected, and the copy reads up to 3 bytes past the end of its buffer. Calling pack_ip_mreq_source() with a source value shorter than 4 bytes copies adjacent heap memory into the returned packed structure.
Relevance: Since the provided CVE description is empty, its relevance to the `node:lts-trixie-slim` image cannot be determined without further details on the affected component. In a general context, a vulnerability in this image would be critical if it allowed remote code execution or a container breakout via the Node.js runtime or underlying Debian Trixie base layers. For normal usage, such a CVE would only become high-risk if your application processes untrusted input that triggers the specific, undefined flaw. (Note: Relevance analysis is automatically generated and may require verification.) Package URL(s):
More Info (NVD): | |||||
| CVE-2026-48959 | high | perl | >0 | not fixed | 7.5 |
| CVE-2026-48962 | high | perl | >0 | not fixed | 7.3 |
| CVE-2026-53655 | medium | pkg:npm/tar@7.5.13 | <=7.5.15 | 7.5.16 | 6.9 |
| CVE-2026-54411 | medium | pam | >0 | not fixed | 6.9 |
| CVE-2026-45149 | medium | pkg:npm/brace-expansion@5.0.5 | >=5.0.0,<5.0.6 | 5.0.6 | 6.5 |
| CVE-2026-7010 | medium | perl | >0 | not fixed | 6.5 |
| CVE-2025-15649 | medium | perl | >0 | not fixed | 5.5 |
| CVE-2026-42338 | medium | pkg:npm/ip-address@10.1.0 | <=10.1.0 | 10.1.1 | 5.3 |
| CVE-2025-45582 | medium | tar | >=1.35+dfsg-3.1 | not fixed | 4.1 |
Severity Levels
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.
About the CVE Scanner
What is a CVE?
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.
About the CVE Scanner
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.
How the CVE Scanner Works
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.
Why CVE Scanning is Essential for Your Docker Images
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.
Benefits of CVE Scanning
- Enhanced Security: Detect and mitigate vulnerabilities before they are exploited.
- Compliance: Meet industry standards and regulatory requirements for secure software.
- Proactive Maintenance: Stay ahead of potential threats by addressing vulnerabilities early.
The Importance of Patching Docker Images
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.
Want to deploy this image?
Try out Sliplane - a simple Docker hosting solution. It provides you with the tools to deploy, manage and scale your containerized applications.
Sliplane is not associated with Docker Inc. or any of its products. Prices do not include VAT.