Scan Another

CVE Scan for gotenberg/gotenberg:8.30.1

Docker image vulnerability scanner

247 Known Vulnerabilities in this Docker Image

7
Critical
72
High
58
Medium
110
Low
0
Info/ Unspecified/ Unknown
CVE IDSeverityPackageAffected VersionFixed VersionCVSS Score
CVE-2026-31789criticalopenssl<3.5.5-1~deb13u23.5.5-1~deb13u29.8

Issue summary: Converting an excessively large OCTET STRING value to a hexadecimal string leads to a heap buffer overflow on 32 bit platforms. Impact summary: A heap buffer overflow may lead to a crash or possibly an attacker controlled code execution or other undefined behavior. If an attacker can supply a crafted X.509 certificate with an excessively large OCTET STRING value in extensions such as the Subject Key Identifier (SKID) or Authority Key Identifier (AKID) which are being converted to hex, the size of the buffer needed for the result is calculated as multiplication of the input length by 3. On 32 bit platforms, this multiplication may overflow resulting in the allocation of a smaller buffer and a heap buffer overflow. Applications and services that print or log contents of untrusted X.509 certificates are vulnerable to this issue. As the certificates would have to have sizes of over 1 Gigabyte, printing or logging such certificates is a fairly unlikely operation and only 32 bit platforms are affected, this issue was assigned Low severity. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.

Relevance:

Given that the provided CVE ID (CVE-2026-31789) refers to a future date and has no specific technical description, its relevance cannot be determined based solely on the provided information. In a standard context, such a vulnerability would typically be critical if it enabled unauthenticated remote code execution or unauthorized filesystem access during the document conversion process. For normal usage, it would likely only pose a risk if the Gotenberg instance is exposed to untrusted user input or malicious files. (Note: Relevance analysis is automatically generated and may require verification.)

Package URL(s):
  • pkg:deb/debian/openssl@3.5.5-1~deb13u1?os_distro=trixie&os_name=debian&os_version=13
CVE-2026-5902criticalchromium<147.0.7727.55-1~deb13u1147.0.7727.55-1~deb13u19.8
CVE-2026-5874criticalchromium<147.0.7727.55-1~deb13u1147.0.7727.55-1~deb13u19.6
CVE-2026-6296criticalchromium<147.0.7727.101-1~deb13u1147.0.7727.101-1~deb13u19.6
CVE-2026-6919criticalchromium<147.0.7727.116-1~deb13u1147.0.7727.116-1~deb13u19.6
CVE-2026-6920criticalchromium<147.0.7727.116-1~deb13u1147.0.7727.116-1~deb13u19.6
CVE-2026-6100criticalpython3.13>0not fixed9.1
CVE-2026-5858highchromium<147.0.7727.55-1~deb13u1147.0.7727.55-1~deb13u18.8
CVE-2026-5859highchromium<147.0.7727.55-1~deb13u1147.0.7727.55-1~deb13u18.8
CVE-2026-5860highchromium<147.0.7727.55-1~deb13u1147.0.7727.55-1~deb13u18.8

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 Icon
About Sliplane

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.

Try Sliplane for free

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.

Connect Github