Is github.com/smallstep/certificates 0.28 vulnerable?
Go · 5 releases from 0.28.0 to 0.28.4 · latest github.com/smallstep/certificates is 0.30.2 · checked 18 Nov 2026
Yes: 8 known advisories
Yes. github.com/smallstep/certificates 0.28.4, the last 0.28 release, is affected by 8 known security advisories (2 critical, 1 medium, 5 low), including CVE-2026-30836, CVE-2025-44005, CVE-2025-66406. Upgrade to 0.30.0 or later to fix all of them.
go get github.com/smallstep/certificates@v0.30.0Is your project on an affected github.com/smallstep/certificates?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting github.com/smallstep/certificates 0.28.4
Step CA affected by an index out of bounds panic in TPM attestation EKU validation in github.com/smallstep/certificates
- Affected
- >=0.24.0 <0.30.0
- Fixed in
- 0.30.0
Step CA affected by an index out of bounds panic in TPM attestation EKU validation
- Affected
- >=0.24.0 <0.30.0
- Fixed in
- 0.30.0
step-ca has Unauthenticated Certificate Issuance via SCEP UpdateReq (MessageType=18) in github.com/smallstep/certificates
- Affected
- <0.30.0
- Fixed in
- 0.30.0
step-ca has Unauthenticated Certificate Issuance via SCEP UpdateReq (MessageType=18)
- Affected
- <0.30.0
- Fixed in
- 0.30.0
Step CA Has Authorization Bypass in ACME and SCEP Provisioners in github.com/smallstep/certificates
- Affected
- <0.29.0
- Fixed in
- 0.29.0
step-ca Has Improper Authorization Check for SSH Certificate Revocation in github.com/smallstep/certificates
- Affected
- <0.29.0
- Fixed in
- 0.29.0
Step CA Has Authorization Bypass in ACME and SCEP Provisioners
- Affected
- <0.29.0
- Fixed in
- 0.29.0
step-ca Has Improper Authorization Check for SSH Certificate Revocation
- Affected
- <0.29.0
- Fixed in
- 0.29.0
Every github.com/smallstep/certificates 0.28.x release
Affected: 0.28.0 to 0.28.4. Latest github.com/smallstep/certificates: 0.30.2.
| Version | Known advisories |
|---|---|
| github.com/smallstep/certificates 0.28.4 | CVE-2026-40097, CVE-2026-40097, CVE-2026-30836, CVE-2026-30836, CVE-2025-44005, CVE-2025-66406, CVE-2025-44005, CVE-2025-66406 |
| github.com/smallstep/certificates 0.28.3 | CVE-2026-40097, CVE-2026-40097, CVE-2026-30836, CVE-2026-30836, CVE-2025-44005, CVE-2025-66406, CVE-2025-44005, CVE-2025-66406 |
| github.com/smallstep/certificates 0.28.2 | CVE-2026-40097, CVE-2026-40097, CVE-2026-30836, CVE-2026-30836, CVE-2025-44005, CVE-2025-66406, CVE-2025-44005, CVE-2025-66406 |
| github.com/smallstep/certificates 0.28.1 | CVE-2026-40097, CVE-2026-40097, CVE-2026-30836, CVE-2026-30836, CVE-2025-44005, CVE-2025-66406, CVE-2025-44005, CVE-2025-66406 |
| github.com/smallstep/certificates 0.28.0 | CVE-2026-40097, CVE-2026-40097, CVE-2026-30836, CVE-2026-30836, CVE-2025-44005, CVE-2025-66406, CVE-2025-44005, CVE-2025-66406 |
Which of your client projects are still on github.com/smallstep/certificates 0.28?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/smallstep/certificates version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/smallstep/certificates versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.