CVE-2025-66406
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. Prior to 0.29.0, there is an improper authorization check for SSH certificate revocation. This affects deployments configured with the SSHPOP provisioner. This vulnerability is fixed in 0.29.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 · moderate confidenceStep CA versions prior to 0.29.0 contain an improper authorization check vulnerability affecting SSH certificate revocation when the SSHPOP provisioner is configured. This could allow an authenticated user to improperly revoke SSH certificates they should not have authority over.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- High
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:H
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 installation and versionRun 'step-ca --version' or check the binary version. Alternatively, check the /etc/step-ca/config/ca.json configuration file for the 'version' field or the software package version installed via the system package manager.Affected if The installed version is lower than 0.29.0 (e.g., 0.28.x, 0.27.x, etc.)
-
Locate Step CA configuration fileThe default configuration is typically at /etc/step-ca/config/ca.json. Open this file and examine the 'provisioners' section.Affected if The configuration file exists and is readable, indicating Step CA is running.
-
Check if SSHPOP provisioner is configuredIn the ca.json configuration file, look for a provisioner entry where 'type' is set to 'SSHPOP' or 'name' contains 'SSHPOP'. Run 'step ca provisioner list' if the CLI is available to enumerate configured provisioners.Affected if An SSHPOP provisioner is present in the configuration - this is the specific provisioner type mentioned in the CVE.
You are affected if your Step CA version is prior to 0.29.0 AND the SSHPOP provisioner is configured in your ca.json file, as the authorization bypass only applies to that provisioner type.
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 · scopedUpgrade Step CA to version 0.29.0 or later. Review SSHPOP provisioner configurations and audit recent certificate revocation events for any unauthorized activity.
0.29.0
- Identify the current Step CA version running in your environment
- Stop the Step CA service
- Upgrade Step CA to version 0.29.0 or later
- Verify the upgrade was successful by checking the version
- Restart the Step CA service
- If using the SSHPOP provisioner, verify the SSH certificate revocation authorization is working correctly after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-66406 — 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-2025-66406 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