CVE-2026-109138: Aliro ValidityIteration check bypassed for certificate-trusted Credential Issuer (fail open)
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 (CONFIGDOORLOCKCREDENTIALISSUERCA) and the Aliro Step-up phase (CONFIGDOORLOCKSTEPUPPHASE) 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Nordic Semiconductor nRF Door Lock and Access Control Add-onto a version that resolves this vulnerability.Fixed in 1.2.0
Event History
Frequently Asked Questions
Which deployments are affected?
Affected deployments use nRF Door Lock and Access Control Add-on versions v1.0.0 through v1.1.1 with both certificate-based Credential Issuer trust (CONFIG_DOOR_LOCK_CREDENTIAL_ISSUER_CA) and the Aliro Step-up phase (CONFIG_DOOR_LOCK_STEP_UP_PHASE) enabled. The default Matter provisioning configuration is not affected.
What does an attacker need to exploit this issue?
The attacker must be a former authorized credential holder with an old Access Document that remains correctly signed by the Credential Issuer. The issuer must have advanced its validity iteration to revoke that credential, and the issuer must be trusted through a certificate chain but not provisioned in the issuer array.
What is the impact of a successful exploit?
A revoked credential can bypass the ValidityIteration credential-rollback check and be accepted, allowing the former holder to gain physical access.
How can this be remediated?
Upgrade to version v1.2.0, where the issue is fixed.