Sigstore
4 CVEs tracked. None of them is in CISA KEV.
This hub aggregates every CVE we track for Sigstore, a product in the oss libraries space. Use it to gauge the current risk picture and drill into individual advisories.
Sigstore CVEs per month
| Month | CVEs |
|---|---|
| 2024-10 | 0 |
| 2024-11 | 0 |
| 2024-12 | 1 |
| 2025-01 | 0 |
| 2025-02 | 0 |
| 2025-03 | 0 |
| 2025-04 | 0 |
| 2025-05 | 0 |
| 2025-06 | 0 |
| 2025-07 | 0 |
| 2025-08 | 0 |
| 2025-09 | 0 |
| 2025-10 | 0 |
| 2025-11 | 0 |
| 2025-12 | 0 |
| 2026-01 | 2 |
| 2026-02 | 0 |
| 2026-03 | 1 |
| 2026-04 | 0 |
| 2026-05 | 0 |
| 2026-06 | 0 |
| 2026-07 | 0 |
| 2026-08 | 0 |
| 2026-09 | 0 |
Severity
How the 4 CVEs score on CVSS. Severity is not exploitation: KEV is counted above.
- High1
- Medium1
Latest CVEs
The 4 most recently published vulnerabilities affecting Sigstore.
- CVE-2026-31830sigstore-ruby verifier returns success for DSSE bundles with mismatched in-toto subject digest7.5
- CVE-2026-24408sigstore has CSRF possibility in OIDC authentication during signing—
- CVE-2026-24137sigstore legacy TUF client allows for arbitrary file writes with target cache path traversal5.8
- CVE-2024-55655sigstore-python has insufficient validation of integration timestamp during verification—
Product grouping is registry-driven, with AI assist and human review. How it works