CVE-2026-109148
CVE-2026-109148 is a high-severity vulnerability with a CVSS 4.0 base score of 7.0. 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: High (CVSS 4.0 base score 7.0)
- EPSS exploit prediction: 0% (3rd percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-324
- Published:
- Last modified:
Description
In 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.
Frequently asked questions
- What is CVE-2026-109148?
- In 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.
- How severe is CVE-2026-109148?
- CVE-2026-109148 has a CVSS 4.0 base score of 7.0, rated high severity.
- Is CVE-2026-109148 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (3rd percentile), an estimate of the probability of exploitation in the next 30 days.
- How do I fix CVE-2026-109148?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
- When was CVE-2026-109148 published?
- CVE-2026-109148 was published on 2026-11-17.
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-2026-131694 — Medium (CVSS 6.6): Tanium addressed an improper check for certificate revocation vulnerability.