Skip to content
Fencer Intel
high 8.3

CVE-2026-109138 json

Aliro ValidityIteration check bypassed for certificate-trusted Credential Issuer (fail open)

published 2d ago modified yesterday also EUVD-2026-126939

cvss
8.3
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.1%
EPSS 0.1% chance of exploitation in 30 days, percentile 0%
public exploits
0
none known

Summary

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, built with Credential Issuer CA certificate-based issuer trust (CONFIG_DOOR_LOCK_CREDENTIAL_ISSUER_CA) and the Aliro Step-up phase (CONFIG_DOOR_LOCK_STEP_UP_PHASE) enabled, AccessManagerImpl::ProcessValidityIteration() treats a failed lookup of the Credential Issuer in the provisioned issuer array as success. For an issuer trusted through a certificate chain but not provisioned, the ValidityIteration (credential-rollback) check is therefore skipped. A former authorized holder with an old but correctly issuer-signed Access Document can be granted physical access after the issuer has advanced its iteration to revoke that credential. The default Matter provisioning configuration is not affected. Fixed in v1.2.0.

Is CVE-2026-109138 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
yesterday

Exploit prediction

0.10% chance of exploitation in the next 30 days, higher than 0% of all scored CVEs (FIRST EPSS, 2026-11-18).

CVSS scores

assigned by version score vector
CNA 4.0 8.3 CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N
CNA 4.0 8.3 CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected products

  • Nordic Semiconductor ASA nRF Door Lock and Access Control Add-on

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.