CVE Scan for jupyterhub/k8s-hub:5.0.0-0.dev.git.7304.he102245a
Docker image vulnerability scanner
69 Known Vulnerabilities in this Docker Image
| CVE ID | Severity | Package | Affected Version | Fixed Version | CVSS Score |
|---|---|---|---|---|---|
| CVE-2026-31958 | high | pkg:pypi/tornado@6.5.4 | <=6.5.4 | 6.5.5 | 8.7 |
In versions of Tornado prior to 6.5.5, the only limit on the number of parts in Tornado 6.5.5 introduces new limits on the size and complexity of multipart bodies, including a default limit of 100 parts per request. These limits are configurable if needed; see Relevance: Given the provided CVE description, this vulnerability is likely highly relevant as it could impact the core authentication or routing functions of the JupyterHub application. It would be critical in multi-tenant environments where an attacker might exploit the flaw to bypass access controls or escalate privileges to gain unauthorized access to other users' notebook servers. For normal usage, risks are highest if the hub is exposed to the public internet without an additional security layer. (Note: Relevance analysis is automatically generated and may require verification.) Package URL(s):
More Info (NVD): | |||||
| CVE-2026-0861 | high | glibc | <2.41-12+deb13u2 | 2.41-12+deb13u2 | 8.4 |
| CVE-2025-15281 | high | glibc | <2.41-12+deb13u2 | 2.41-12+deb13u2 | 7.5 |
| CVE-2026-0915 | high | glibc | <2.41-12+deb13u2 | 2.41-12+deb13u2 | 7.5 |
| CVE-2026-1519 | high | bind9 | <1:9.20.21-1~deb13u1 | 1:9.20.21-1~deb13u1 | 7.5 |
| CVE-2026-27135 | high | nghttp2 | <=1.64.0-1.1 | not fixed | 7.5 |
| CVE-2026-30922 | high | pkg:pypi/pyasn1@0.6.2 | <=0.6.2 | 0.6.3 | 7.5 |
| CVE-2026-32597 | high | pkg:pypi/pyjwt@2.11.0 | <=2.11.0 | 2.12.0 | 7.5 |
| CVE-2026-33412 | medium | vim | <=2:9.1.1230-2 | not fixed | 5.6 |
| CVE-2026-29111 | medium | systemd | <=257.9-1~deb13u1 | not fixed | 5.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.