CVE-2026-131694
Tanium addressed an improper check for certificate revocation vulnerability.
CVSS
6.6
Média
EPSS
—
KEV
—
Exploit Today
—
0-100
Publicado: 18 de nov. de 2026 · Última mod.: 18 de nov. de 2026 · CWE-324
Ainda não há histórico EPSS suficiente.
Tanium addressed an improper check for certificate revocation vulnerability.
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2026-109148—10.7%
——3In the Aliro access control reference
applications of the Nordic Semiconductor nRF Door Lock and Access Control
Add-on v1.0.0 through v1.1.1, the stored Access Document record does not
retain validFrom and validUntil. The cached public key path (VerifyPublicKey())
and the Kpersistent fast path (_VerifyKPersistentKey()) therefore never
re-evaluate the Access Document validity period. An attacker who held a
time-limited Aliro credential that was valid when first presented can
continue to obtain physical access after the Access Document has expired, for
as long as the cached record remains available. Fixed in v1.2.0.1dCVE-2026-399238.1 ALT37.6%
——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.26dCVE-2026-547873.1 BAI2.9%
——1sigstore-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.26dCVE-2026-528096.8 MÉD8.8%
——3Gogs is an open source self-hosted Git service. Prior to 0.14.3, password-reset tokens are generated using conf.Auth.ActivateCodeLives (the account-activation lifetime), not conf.Auth.ResetPasswordCodeLives. The token lifetime is baked into the token itself at generation time and is re-extracted from the token at verification time, making RESET_PASSWORD_CODE_LIVES irrelevant to actual enforcement. When an administrator configures a shorter reset window (e.g., 10 minutes) for compliance or security reasons, reset tokens remain exploitable for the full activation lifetime instead, while the reset email falsely advertises the shorter expiry. This vulnerability is fixed in 0.14.3.15dCVE-2025-330126.3 MÉD6.7%
——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.42d