CVSS 3.1
10.0 criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:NCritical (10.0) in smallstep step-ca. EPSS 9.4% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/smallstep/certificates 0.29.0.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:Ngithub.com/smallstep/certificates (Go): fixed in 0.29.0Explain CVE-2025-44005 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-44005?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-44005?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-44005 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| smallstep Step-CA | 0.28.4 |
| smallstep Step-CA | v0.28.3 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-h8cp-697h-8c8p | Go | github.com/smallstep/certificates | <0.29.0 | 0.29.0 |
| GO-2025-4180 | Go | github.com/smallstep/certificates | <0.29.0 | 0.29.0 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| SUSE | Linux Enterprise Module for Package Hub 15 SP6 | govulncheck-vulndb | 0.0.20251209T172047-150000.1.127.1 | SUSE-SU-2025:4395-1 |
| openSUSE | Leap 15.6 | govulncheck-vulndb | 0.0.20251209T172047-150000.1.127.1 | SUSE-SU-2025:4395-1 |
| openSUSE | Leap 16.0 | govulncheck-vulndb | 0.0.20260723T184607-160000.1.1 | openSUSE-SU-2026:21483-1 |
| Alpine | v3.22, v3.23, v3.24 | step-certificates | 0.29.0-r0 | ALPINE-CVE-2025-44005 |
From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: SUSE · openSUSE · Alpine.
Red Hat rates this Critical.
No Red Hat products are impacted, because the affected component (Step CA) is not used or provided by any products.
This vulnerability was marked as a Critical vulnerability because it allows a remote, unauthenticated attacker to bypass core authorization mechanisms of a Certificate Authority and directly issue trusted certificates, fundamentally breaking the CA trust boundary. While the flaw does not lead to arbitrary code execution on the Step CA host, compromising a CA’s issuance process is equivalent to a system-level security failure, as attackers can mint certificates for unauthorized identities and use them for large-scale impersonation, man-in-the-middle attacks, and interception of encrypted traffic across systems beyond the CA itself. The attack requires no privileges, no user interaction, and low complexity, and its effects propagate outside the vulnerable system due to the implicit trust placed in issued certificates, resulting in a scope change and high confidentiality and integrity impact. This ability to undermine PKI trust at scale elevates the flaw beyond an Important issue and justifies a Critical severity classification from a technical risk standpoint.
No mitigation is currently available that meets Red Hat Product Security’s standards for usability, deployment, applicability, or stability.
But the exposure can be minimized by restricting or blocking access to the /sign endpoint through network controls or reverse proxies.
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-44005.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.