CVE
nRF Door Lock and Access Control Add-on expired Aliro credential accepted on cached access paths
CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.21% · 10th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 12/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
The Nordic Semiconductor nRF Door Lock and Access Control Add-on's Aliro reference applications keep honoring an expired Access Document on cached and fast access paths, because the stored record does not keep its validity dates. An attacker on an adjacent network, without logging in or any user action, can keep gaining physical access with a time-limited Aliro credential after it expires, for as long as the cached record remains available.
Written by a model from the sources below. Verify against them.
Original 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.
cve.now Index
- Exploitation0/40No signal
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity7/10CVSS 7.0
- No patch5/5No patch listed yet
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 34 if advisories confirm default setups are exposed
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-109148 (Expired Aliro Access Document remains authorized on cached and fast access paths), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-109148 (entry last updated 2026-11-17):
Affected:
- Nordic Semiconductor ASA nRF Door Lock and Access Control Add-on: versions v1.0.0 through v1.1.1 (inclusive). Fixed in v1.2.0.
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-109148 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-109148 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://docs.nordicsemi.com/r/bundle/struct_sa/page/struct/sa.html
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-109148
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-109148"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Nordic Semiconductor ASA nRF Door Lock and Access Control Add-on
v1.0.0 through v1.1.1 (inclusive). Fixed in v1.2.0.
Evidence 3
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-109148
Is CVE-2026-109148 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-109148?
nRF Door Lock and Access Control Add-on: version v1.0.0 through v1.1.1 (inclusive). Fixed in v1.2.0..Source: cve.now feed data