| CVE ID | Severity | Package | Affected Version | Fixed Version | CVSS Score |
|---|---|---|---|---|---|
| CVE-2026-30836 | critical | certificates | <0.30.0 | 0.30.0 | 10.0 |
SummaryAn attacker can force a Step CA SCEP provisioner to create certificates without completing certain protocol authorization checks. DetailsSCEP requests carry a message type. On receipt of a SCEP request, Step CA starts processing it by parsing its contents. Message types that were considered valid, but not explicitly supported in Step CA, would result in getting parsed successfully. While processing the parsed SCEP message, authorization logic would be skipped for the non-supported message types. As a result, the request would be treated as authorized, bypassing the authorization checks normally enforced as part of the SCEP protocol and its implementation in Step CA. Authorization webhooks and regular CA policies, such as allowed names and restrictions on certificate validity periods, remain in place. MitigationsIf you are unable to upgrade to v0.30.0 or newer, the attack can be mitigated by (temporarily) disabling or removing SCEP provisioners, or restricting access to SCEP provisioners to trusted clients only. FixIn v0.30.0, additional validation was added to SCEP provisioners, so that they reject unsupported message types. AcknowledgementsThis issue was identified and reported by Prasanth Sundararajan. Embargo ListIf your organization runs Step CA in production and would like advance, embargoed notification of future security updates, visit https://u.step.sm/disclosure to request inclusion on our embargo list. Stay safe, and thank you for helping us keep the ecosystem secure. If you have urgent questions, please contact security@smallstep.com. Relevance: The relevance of this vulnerability depends on whether it affects Caddy’s core HTTP/S functionality or an optional module, as "normal usage" typically involves basic reverse proxying and static file serving. It would be critical in scenarios where an attacker can exploit the specific flaw to achieve unauthorized access, information disclosure, or a denial of service within a production environment. Without further details on the vulnerability's vector, users should assume high relevance if their configuration utilizes the specific component targeted by the CVE. (Note: Relevance analysis is automatically generated and may require verification.) Package URL(s):
More Info (NVD): | |||||
| CVE-2026-31789 | critical | openssl | <3.5.6-r0 | 3.5.6-r0 | 9.8 |
| CVE-2026-33186 | critical | grpc | <1.79.3 | 1.79.3 | 9.1 |
| CVE-2026-33810 | high | pkg:golang/stdlib@1.26.0 | >=1.26.0-0,<1.26.2 | 1.26.2 | 8.2 |
| CVE-2026-28387 | high | openssl | <3.5.6-r0 | 3.5.6-r0 | 8.1 |
| CVE-2026-30851 | high | caddy | >=2.10.0,<2.11.2 | 2.11.2 | 8.1 |
| CVE-2026-40200 | high | musl | <1.2.5-r23 | 1.2.5-r23 | 8.1 |
| CVE-2026-25679 | high | pkg:golang/stdlib@1.26.0 | >=1.26.0-0,<1.26.1 | 1.26.1 | 7.5 |
| CVE-2026-2673 | high | openssl | <3.5.6-r0 | 3.5.6-r0 | 7.5 |
| CVE-2026-27135 | high | nghttp2 | <=1.68.0-r0 | not fixed | 7.5 |
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.
Try out Sliplane - a simple Docker hosting solution. It provides you with the tools to deploy, manage and scale your containerized applications.