FlawAtlas
Search the atlas
CVE-2026-30836 Critical

step-ca has Unauthenticated Certificate Issuance via SCEP UpdateReq (MessageType=18) in github.com/smallstep/certificates

step-ca has Unauthenticated Certificate Issuance via SCEP UpdateReq (MessageType=18) in github.com/smallstep/certificates

Exploit probability 0.3%
Published March 23, 2026
Required by Not available
Last source change March 31, 2026

02 / AFFECTED SOFTWARE

Affected packages

Unknown Unknown

7 explicit affected versions

Go github.com/smallstep/certificates
Go github.com/smallstep/certificates

03 / CONNECTIONS

Connected vulnerabilities

related OPENSUSE-SU-2026:21483-1

04 / EVIDENCE

Source records

Open Source Vulnerabilities CVE-2026-30836

Step CA is an online certificate authority for secure, automated certificate management for DevOps. Versions 0.30.0-rc6 and below do not safeguard against unauthenticated certificate issuance through the SCEP UpdateReq. This issue has been fixed in version 0.30.0.

View original source
Open Source Vulnerabilities GHSA-q4r8-xm5f-56gw

## Summary An attacker can force a Step CA SCEP provisioner to create certificates without completing certain protocol authorization checks. ## Details SCEP 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. ## Mitigations If 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. ## Fix In v0.30.0, additional validation was added to SCEP provisioners, so that they reject unsupported message types. ## Acknowledgements This issue was identified and reported by Prasanth Sundararajan. ## Embargo List If 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 [[email protected]](mailto:[email protected]).

View original source
Open Source Vulnerabilities GO-2026-4775

step-ca has Unauthenticated Certificate Issuance via SCEP UpdateReq (MessageType=18) in github.com/smallstep/certificates

View original source

05 / REFERENCES

Further evidence