CVE Scan for amazon/aws-for-fluent-bit:stable
Docker image vulnerability scanner
10 Known Vulnerabilities in this Docker Image
| CVE ID | Severity | Package | Affected Version | Fixed Version | CVSS Score |
|---|---|---|---|---|---|
| CVE-2025-65637 | high | logrus | =1.9.0 | 1.9.1 | 8.7 |
A denial-of-service vulnerability exists in github.com/sirupsen/logrus when using Entry.Writer() to log a single-line payload larger than 64KB without newline characters. Due to limitations in the internal bufio.Scanner, the read fails with "token too long" and the writer pipe is closed, leaving Writer() unusable and causing application unavailability (DoS). This affects versions < 1.8.3, 1.9.0, and 1.9.2. The issue is fixed in 1.8.3, 1.9.1, and 1.9.3+, where the input is chunked and the writer continues to function even if an error is logged. Relevance: The CVE-2025-65637 could be critical if the vulnerability allows remote code execution or privilege escalation within the `amazon/aws-for-fluent-bit:stable` image, particularly in multi-tenant environments where attackers could exploit it to access sensitive logs or AWS credentials. It becomes less relevant if the image is used in isolated, read-only deployments with restricted network access. Always verify the specific impact and patch status for your use case. (Note: Relevance analysis is automatically generated and may require verification.) Package URL(s):
More Info (NVD): | |||||
| CVE-2024-24786 | medium | protobuf | <1.33.0 | 1.33.0 | 6.6 |
| CVE-2020-8911 | medium | aws-sdk-go | >=0 | not fixed | 5.6 |
| CVE-2025-11468 | medium | python-libs | <2.7.18-1.amzn2.0.16 | 2.7.18-1.amzn2.0.16 | 4.1 |
| CVE-2026-0672 | medium | python-libs | <2.7.18-1.amzn2.0.16 | 2.7.18-1.amzn2.0.16 | 4.1 |
| CVE-2026-0865 | medium | python-libs | <2.7.18-1.amzn2.0.16 | 2.7.18-1.amzn2.0.16 | 4.1 |
| CVE-2025-15282 | medium | python-libs | <2.7.18-1.amzn2.0.16 | 2.7.18-1.amzn2.0.16 | 4.1 |
| CVE-2025-6075 | medium | python-libs | <2.7.18-1.amzn2.0.16 | 2.7.18-1.amzn2.0.16 | 4.1 |
| CVE-2026-1757 | low | libxml2 | <2.9.1-6.amzn2.5.24 | 2.9.1-6.amzn2.5.24 | 3.1 |
| CVE-2020-8912 | low | aws-sdk-go | >=0 | not fixed | 2.5 |
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.