How severe is CVE-2026-54787?

CVE-2026-54787 has a CVSS 3.x base score of 3.1, rated low severity. It is exploitable over network with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability none.

Is CVE-2026-54787 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (1st percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-54787?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2026-54787 published?

CVE-2026-54787 was published on 2026-07-31 and last updated on 2026-08-01.

CVE-2026-54787

CVE-2026-54787 is a low-severity vulnerability with a CVSS 3.x base score of 3.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-324.

Key facts

Severity: Low (CVSS 3.x base score 3.1)
EPSS exploit prediction: 0% (1st percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-324
Published: 2026-07-31
Last modified: 2026-08-01

Description

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.

Frequently asked questions

What is CVE-2026-54787?: 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.
How severe is CVE-2026-54787?: CVE-2026-54787 has a CVSS 3.x base score of 3.1, rated low severity. It is exploitable over network with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability none.
Is CVE-2026-54787 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (1st percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-54787?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2026-54787 published?: CVE-2026-54787 was published on 2026-07-31 and last updated on 2026-08-01.

References

Other CWE-324 vulnerabilities

CVE-2024-36031 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: keys: Fix overwrite of key expiration on…
CVE-2025-31123 — High (CVSS 8.7): Zitadel is open-source identity infrastructure software. A vulnerability existed where expired keys can be used to…
CVE-2026-39923 — High (CVSS 8.1): Flarum before 1.8.16 contains a password reset token expiry bypass vulnerability that allows unauthenticated attackers…
CVE-2025-2291 — High (CVSS 8.1): Password can be used past expiry in PgBouncer due to auth_query not taking into account Postgres its VALID UNTIL value,…
CVE-2026-52809 — Medium (CVSS 6.8): Gogs is an open source self-hosted Git service. Prior to 0.14.3, password-reset tokens are generated using…
CVE-2024-25679 — Medium (CVSS 6.5): In PQUIC before 5bde5bb, retention of unused initial encryption keys allows attackers to disrupt a connection with a…

Browse all CWE-324 vulnerabilities →