CVE-2024-29916

What it is

The dormakaba Saflok system before the November 2023 software update allows an attacker to unlock arbitrary doors at a property via forged keycards, if the attacker has obtained one active or expired keycard for the specific property, aka the "Unsaflok" issue. This occurs, in part, because the key derivation function relies only on a UID. This affects, for example, Saflok MT, and the Confidant, Quantum, RT, and Saffire series.

At a glance

Exploitability

Can be exploited with physical access without logging in, but needs a user to act. High risk of data exposure, data tampering.

Exploit odds

0.3% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2024-03-21 17:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 07:23 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.3% in the next 30 days (EPSS).
• Severity: 5.6 MEDIUM (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2024-03-21 17:15 UTC

Last modified

2026-06-17 07:23 UTC

Exploit probability

0.3% · EPSS, next 30 days

Weakness

CWE-407

Record status

Deferred

Attack profile CVSS 3.1 · 5.6

Attack vector

Physical

Complexity

High

Privileges needed

None

User interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2024-29916.md and follow it. Check whether this project is affected by CVE-2024-29916. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge