| CVE ID | Severity | Package | Affected Version | Fixed Version | CVSS Score |
|---|---|---|---|---|---|
| CVE-2025-69421 | high | openssl | <3.0.18-1~deb12u2 | 3.0.18-1~deb12u2 | 7.5 |
Issue summary: Processing a malformed PKCS#12 file can trigger a NULL pointer dereference in the PKCS12_item_decrypt_d2i_ex() function. Impact summary: A NULL pointer dereference can trigger a crash which leads to Denial of Service for an application processing PKCS#12 files. The PKCS12_item_decrypt_d2i_ex() function does not check whether the oct parameter is NULL before dereferencing it. When called from PKCS12_unpack_p7encdata() with a malformed PKCS#12 file, this parameter can be NULL, causing a crash. The vulnerability is limited to Denial of Service and cannot be escalated to achieve code execution or memory disclosure. Exploiting this issue requires an attacker to provide a malformed PKCS#12 file to an application that processes it. For that reason the issue was assessed as Low severity according to our Security Policy. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#12 implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.
Relevance: The relevance of CVE-2025-69421 depends on the specific vulnerabilities it addresses; if it targets NGINX core functionality or dependencies in nginxinc/nginx-unprivileged:1.28-bookworm, it could be critical in scenarios involving untrusted inputs or exposed endpoints. If the vulnerability is unrelated to NGINX or its default configuration in this image, it may have minimal impact. Always verify the CVE details against the specific usage and deployment context. (Note: Relevance analysis is automatically generated and may require verification.) Package URL(s):
More Info (NVD): | |||||
| CVE-2025-69420 | high | openssl | <3.0.18-1~deb12u2 | 3.0.18-1~deb12u2 | 7.5 |
| CVE-2025-69419 | high | openssl | <3.0.18-1~deb12u2 | 3.0.18-1~deb12u2 | 7.4 |
| CVE-2026-25210 | medium | expat | <=2.5.0-1+deb12u2 | not fixed | 6.9 |
| CVE-2026-22795 | medium | openssl | <3.0.18-1~deb12u2 | 3.0.18-1~deb12u2 | 5.5 |
| CVE-2026-22796 | medium | openssl | <3.0.18-1~deb12u2 | 3.0.18-1~deb12u2 | 5.3 |
| CVE-2025-68160 | medium | openssl | <3.0.18-1~deb12u2 | 3.0.18-1~deb12u2 | 4.7 |
| CVE-2025-45582 | medium | tar | >=1.34+dfsg-1.2+deb12u1 | not fixed | 4.1 |
| CVE-2025-69418 | medium | openssl | <3.0.18-1~deb12u2 | 3.0.18-1~deb12u2 | 4.0 |
| CVE-2025-8176 | low | tiff | <=4.5.0-6+deb12u3 | 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.