Step CaApplication · Smallstep
CVE-2026-30836
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedStep 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceStep CA versions 0.30.0-rc6 and below contain a critical authentication bypass in the SCEP (Simple Certificate Enrollment Protocol) UpdateReq handler, allowing unauthenticated attackers to issue arbitrary certificates from the CA. This enables complete PKI compromise including impersonation and man-in-the-middle attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Step CaApplication
< 0.30.0= 0.30.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Step CA versionRun 'step ca version' or check the Docker/container image tag, or inspect the binary with 'step --version'Affected if Version is 0.30.0-rc6 or below, or version 0.30.0 exactly (note: 0.30.0 is also affected)
-
Confirm SCEP provisioner is enabledCheck Step CA configuration file (typically config/ca.json) for a provisioner with type 'SCEP' in the provisioners arrayAffected if A provisioner with type 'SCEP' exists in the configuration
-
Inspect SCEP provisioner settingsReview the SCEP provisioner configuration block for the 'updateRequest' handler or 'enabled' flags - look for any settings related to UpdateReqAffected if The UpdateReq handler or SCEP endpoint is enabled without additional authentication controls
-
Check SCEP endpoint exposureVerify network exposure of the SCEP endpoint - typically at /scep/ paths on the Step CA port (default 443 or 8443) - check firewall rules and reverse proxy configurationAffected if The SCEP endpoint is exposed to untrusted networks or the internet
-
Review certificate issuance logsExamine Step CA audit logs or certificate authority logs for any certificate issuances from SCEP provisioner that were not initiated by legitimate clients - look for unexpected 'certificate.authorize' events with SCEP provisionerAffected if Certificate issuance events exist from SCEP provisioner that are not attributable to authorized client activity
Your environment is affected if Step CA version is below 0.30.0 (including 0.30.0 itself) AND the SCEP provisioner is enabled, as this combination allows unauthenticated certificate issuance via the vulnerable UpdateReq handler.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.30.0
Upgrade Step CA to version 0.30.0 or later which includes the fix for unauthenticated SCEP certificate issuance. Audit issued certificates for any unauthorized issuance and consider revoking suspicious certificates.
Step CA version 0.30.0 or later
- 1. Identify current Step CA version using 'step ca version' or checking the deployed container/binary version
- 2. Stop the Step CA service to prevent continued vulnerable operation
- 3. Backup the Step CA configuration directory (typically located at /etc/step-ca or ~/step-ca)
- 4. Upgrade Step CA to version 0.30.0 or later by downloading the new release from the official GitHub repository
- 5. Verify the upgrade by running 'step ca version' and confirming it shows 0.30.0 or higher
- 6. Restart the Step CA service
- 7. Verify the SCEP endpoint now requires proper authentication by reviewing logs or testing with an unauthenticated request
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Step Ca
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30836 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-30836 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data