CVE-2026-109148: Nordic Semiconductor ASA nRF Door Lock and Access Control Add-on · Use of a Key Past its Expiration Date
Affects Nordic Semiconductor ASA nRF Door Lock and Access Control Add-onSource CVE Database V5
Not known to be exploited · CVSS 7.0 High · fixed in 1.2.0 : patch Nordic Semiconductor ASA nRF Door Lock and Access Control Add-on soon.
Data as of 17 Nov 2026, 09:05 UTC
Thin evidence
One scorer or none| CNA (YesWeHack) | CVSS 4.0 | 7.0 |
|---|
- Patch
- Available – fixed in 1.2.0
CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Nordic Semiconductor ASAnRF Door Lock and Access Control Add-on | Affected
| Fixed in– |
AI-suggested
Upgrade to Nordic Semiconductor nRF Door Lock and Access Control Add-on version 1.2.0 or later, where this issue is fixed. No other mitigation is indicated.
Description
CVE-2026-109148 affects the Aliro access control reference applications in Nordic Semiconductor's nRF Door Lock and Access Control Add-on versions 1.0.0 through 1.1.1. The vulnerability arises because the stored Access Document record does not retain the validity period fields validFrom and validUntil. Consequently, cached public keys are not re-validated against expiration, allowing an attacker with a previously valid time-limited credential to maintain physical access beyond the intended expiration. This issue is fixed in version 1.2.0.