CVE-2026-54787

See a problem?
Please try reporting it to the source first.
Source
https://cve.org/CVERecord?id=CVE-2026-54787
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-54787.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-54787
Aliases
Downstream
Related
Published
2026-07-31T21:58:14.156Z
Modified
2026-08-02T03:47:27.939376696Z
Severity
  • 3.1 (Low) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N CVSS Calculator
Summary
sigstore-go fails to check signature timestamps against a signing key's validity period
Details

sigstore-go is a Go library for Sigstore signing and verification. Prior to 1.2.1, sigstore-go does not check a bundle signing timestamp against the validity window of an ExpiringKey wrapping a self-managed long-lived signing key without a certificate, which can allow an attacker holding expired key material to sign accepted bundles. This issue is fixed in version 1.2.1.

Database specific 
{
    "cwe_ids": [
        "CWE-324"
    ],
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/54xxx/CVE-2026-54787.json",
    "cna_assigner": "GitHub_M"
}
References

Affected packages

Git / github.com/sigstore/sigstore-go

Affected ranges

Type
GIT
Repo
https://github.com/sigstore/sigstore-go
Events
Introduced
0 Unknown introduced commit / All previous commits are affected
Fixed
4594ab4c779d08be1f4419803a8249188f35ed5f
Database specific 
{
    "source": [
        "AFFECTED_FIELD",
        "REFERENCES"
    ],
    "extracted_events": [
        {
            "introduced": "0"
        },
        {
            "fixed": "1.2.1"
        }
    ]
}

Affected versions

v0.*
v0.1.0
v0.2.0
v0.3.0
v0.4.0
v0.5.0
v0.5.1
v0.6.0
v0.6.1
v0.6.2
v0.7.0
v0.7.1
v0.7.2
v0.7.3
v1.*
v1.0.0
v1.1.0
v1.1.1
v1.1.2
v1.1.3
v1.1.4
v1.2.0

Database specific

source 
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-54787.json"