CVE-2026-109154: Matter door lock credential validation accepts credentials of disabled or unresolved users
In the Matter door lock applications of the Nordic Semiconductor nRF Door Lock and Access Control Add-on v1.0.0 through v1.1.1, AccessManager::ValidateCredential() checks only credential occupancy and the secret bytes, and never reads the owning user's UserStatus. It also returns success when no owning user can be resolved. A user suspended by setting their status to OccupiedDisabled can continue to unlock the door with their previously assigned credential, and an orphaned but occupied credential is also accepted. Fixed in v1.2.0.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in v1.2.0
Event History
Frequently Asked Questions
Which deployments are affected?
Matter door lock applications using Nordic Semiconductor nRF Door Lock and Access Control Add-on versions 1.0.0 through 1.1.1 are affected. Version 1.2.0 contains the fix.
What does an attacker need to exploit this issue?
The attacker needs a previously assigned valid credential for a user that has been disabled, or an occupied credential whose owning user can no longer be resolved. The credential must contain the expected secret bytes.
Does disabling a user revoke that user's existing door credential?
No. In affected versions, a user set to OccupiedDisabled can still unlock the door with a previously assigned credential because validation does not check the user's status.
What is the risk from orphaned credentials?
An occupied credential is accepted even when its owning user cannot be resolved. This can allow a credential to continue unlocking the door after its user association is missing.
What should be done if updating is not immediately possible?
Remove or replace credentials assigned to users that are being disabled, and identify occupied credentials without a resolvable owning user. Upgrade to version 1.2.0 when possible.