CVE-2026-109138: Aliro ValidityIteration check bypassed for certificate-trusted Credential Issuer (fail open)

Published Nov 17, 2026
·
Updated

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

1 affected component
Nordic Semiconductor nRF Door Lock and Access Control Add-on>=1.0.0<=1.1.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Nordic Semiconductor nRF Door Lock and Access Control Add-on to a version that resolves this vulnerability.

    Fixed in 1.2.0

Event History

Nov 17, 2026
CVE Published
via MITRE·08:46 AM
Data Sourced
via MITRE·08:46 AM
DescriptionWeakness

Frequently Asked Questions

1

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.

2

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.

3

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.

4

How can this be remediated?

Upgrade to version v1.2.0, where the issue is fixed.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203