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 aga
CVSS
3.1
Bajo
EPSS
0.1%
p3
KEV
—
Exploit Today
1
0-100
Publicado: 31 jul 2026 · Última mod.: 23 oct 2026 · CWE-324
0.1%EPSS · 30 días0.1%
2026-09-282026-10-25
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.
- github.comhttps://github.com/sigstore/sigstore-go/commit/4594ab4c779d08be1f4419803a8249188f35ed5f
- github.comhttps://github.com/sigstore/sigstore-go/pull/642
- github.comhttps://github.com/sigstore/sigstore-go/releases/tag/v1.2.1
- github.comhttps://github.com/sigstore/sigstore-go/security/advisories/GHSA-wqqc-jjcq-vfxm
- github.comhttps://github.com/sigstore/sigstore-go/security/advisories/GHSA-wqqc-jjcq-vfxm
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2026-399238.1 ALT36.8%
——11Flarum before 1.8.16 contains a password reset token expiry bypass vulnerability that allows unauthenticated attackers to reuse expired password reset tokens by submitting them directly to the reset processing endpoint. The SavePasswordController::handle() method calls PasswordToken::findOrFail() without performing any expiry validation, allowing attackers to bypass the 24-hour token lifetime enforced only during form rendering and change any account's password to gain an authenticated session.4dCVE-2025-330126.3 MED6.6%
——2IBM Db2 10.5.0 through 10.5.11, 11.1.0 through 11.1.4.7, 11.5.0 through 11.5.9, and 12.1.0 through 12.1.3 for Linux could allow an authenticated user to regain access after account lockout due to password use after expiration date.20d