CVE-2025-59097: dormakaba Access Manager 92xx-k5 · Missing Authentication
Affects dormakaba Access Manager 92xx-k5Source CVE Database V5
Not known to be exploited · CVSS 9.3 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 26 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| dormakabaAccess Manager 92xx-k5 | Affected
| Fixed in– |
| dormakabaAccess Manager 92xx-k7 | Affected
| Fixed in– |
AI-suggested
To mitigate this vulnerability, European organizations should immediately verify whether dormakaba Access Manager 92xx-K5 devices are deployed in their environment and assess their network exposure. The following specific actions are recommended: 1) Enable IPsec authentication on all 92xx-K5 devices to enforce authentication and authorization on SOAP configuration requests. 2) If possible, upgrade to or configure devices supporting mTLS for stronger mutual authentication. 3) Implement strict network segmentation to isolate access control devices from general IT networks and untrusted zones. 4) Deploy internal firewalls and access control lists to restrict network-level access to these devices only to authorized management systems. 5) Conduct thorough network scans to identify any devices exposed directly to the internet and immediately remove or secure them. 6) Regularly audit access control configurations and monitor logs for unauthorized changes. 7) Engage with dormakaba support for any available patches or updated firmware addressing this issue. 8) Train security and IT staff on the risks of default insecure configurations and the importance of enabling authentication features. These targeted mitigations go beyond generic advice by focusing on the specific insecure default configuration and network exposure vectors.
Description
The exos 9300 application can be used to configure Access Managers (e.g.92xx, 9230 and 9290). The configuration is done in a graphical user interface on the dormakaba exos server. As soon as the save button is clicked in exos 9300, the whole configuration is sent to the selected Access Manager via SOAP. The SOAP request is sent without any prior authentication or authorization by default. Though authentication and authorization can be configured using IPsec for 92xx-K5 devices and mTLS for 92xx-K7 devices, it is not enabled by default and must therefore be activated with additional steps. This insecure default allows an attacker with network level access to completely control the whole environment. An attacker is for example easily able to conduct the following tasks without prior authentication: - Re-configure Access Managers (e.g.remove alarming system requirements) - Freely re-configure the inputs and outputs - Open all connected doors permanently - Open all doors for a defined time interval - Change the admin password - and many more Network level access can be gained due to an insufficient network segmentation as well as missing LAN firewalls. Devices with an insecure configuration have been identified to be directly exposed to the internet.