CVE Scan for redis:8
Docker image vulnerability scanner
31 Known Vulnerabilities in this Docker Image
| CVE ID | Severity | Package | Affected Version | Fixed Version | CVSS Score |
|---|---|---|---|---|---|
| CVE-2026-31790 | high | openssl | <3.5.5-1~deb13u2 | 3.5.5-1~deb13u2 | 7.5 |
Issue summary: Applications using RSASVE key encapsulation to establish a secret encryption key can send contents of an uninitialized memory buffer to a malicious peer. Impact summary: The uninitialized buffer might contain sensitive data from the previous execution of the application process which leads to sensitive data leakage to an attacker. RSA_public_encrypt() returns the number of bytes written on success and -1 on error. The affected code tests only whether the return value is non-zero. As a result, if RSA encryption fails, encapsulation can still return success to the caller, set the output lengths, and leave the caller to use the contents of the ciphertext buffer as if a valid KEM ciphertext had been produced. If applications use EVP_PKEY_encapsulate() with RSA/RSASVE on an attacker-supplied invalid RSA public key without first validating that key, then this may cause stale or uninitialized contents of the caller-provided ciphertext buffer to be disclosed to the attacker in place of the KEM ciphertext. As a workaround calling EVP_PKEY_public_check() or EVP_PKEY_public_check_quick() before EVP_PKEY_encapsulate() will mitigate the issue. The FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.1 and 3.0 are affected by this issue. Relevance: Since the provided description is missing, it is impossible to determine the specific technical impact; however, any CVE for a core database like Redis 8 typically involves memory safety, data exposure, or remote code execution. It would be most critical in production environments where the Redis instance is exposed to untrusted networks or used as a primary cache for sensitive session data. For "normal" usage behind a secure firewall with authenticated access, the relevance depends on whether the vulnerability can be triggered by standard commands or requires administrative privileges. (Note: Relevance analysis is automatically generated and may require verification.) Package URL(s):
More Info (NVD): | |||||
| CVE-2026-5704 | medium | tar | <=1.35+dfsg-3.1 | not fixed | 5.0 |
| CVE-2025-45582 | medium | tar | >=1.35+dfsg-3.1 | not fixed | 4.1 |
| CVE-2026-28387 | unspecified | openssl | <3.5.5-1~deb13u2 | 3.5.5-1~deb13u2 | 3.1 |
| CVE-2026-28388 | unspecified | openssl | <3.5.5-1~deb13u2 | 3.5.5-1~deb13u2 | 3.1 |
| CVE-2026-28389 | unspecified | openssl | <3.5.5-1~deb13u2 | 3.5.5-1~deb13u2 | 3.1 |
| CVE-2026-28390 | unspecified | openssl | <3.5.5-1~deb13u2 | 3.5.5-1~deb13u2 | 3.1 |
| CVE-2026-31789 | unspecified | openssl | <3.5.5-1~deb13u2 | 3.5.5-1~deb13u2 | 3.1 |
| CVE-2005-2541 | low | tar | <=1.35+dfsg-3.1 | not fixed | 3.1 |
| CVE-2007-5686 | low | shadow | <=1:4.17.4-2 | not fixed | 3.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.