Critical Authentication

CVE-2025-59097 — Unauthenticated SOAP API in dormakaba access manager

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.

Published Jan 26, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: SEC-VLab

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.7% (30-day exploitation probability)+8
Technical severity (critical)+10
Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.66%

ahead of 50% of scored CVEs · Oct 14, 2026

Affects

Dormakaba

Access Manager 92xx-k5 and 1 more

CVSS base

9.3

Critical · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

Yes

can an attacker script the kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Dormakaba Access Manager 92xx-k5, Dormakaba Access Manager 92xx-k7).
The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes matching the vulnerability class (authentication), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Dormakaba	Access Manager 92xx-k5	version 92xx-K5: All Versions	Vulnerable	CVE Program (cve.org) e CISA ADP
Dormakaba	Access Manager 92xx-k7	version 92xx-K7: Older than BAME 06.00 must be configured	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Attack requirements

None

Privileges required

None

User interaction

None

Scope

Confidentiality (vulnerable system)

High

Integrity (vulnerable system)

High

Availability (vulnerable system)

High

Confidentiality (subsequent)

None

Integrity (subsequent)

None

Availability (subsequent)

None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
9.3	CVSS 4.0	Critical	—	—	551230f0-3615-47bd-b7cc-93e92e730bbf via NIST National Vulnerability Database
9.3	CVSS 4.0	Critical	—	—	SEC-VLab via CVE Program (cve.org) e CISA ADP

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

(score shown at the top: 551230f0-3615-47bd-b7cc-93e92e730bbf)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-306 · Missing Authentication for Critical Function

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.66%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Review authentication logs: logins without MFA, anomalous sessions and recently created accounts.

web/proxy/WAF logsnetwork IDS/IPSauthentication logs

Timeline

What happened to this CVE, newest first.

2026
Affected products added · dormakaba/access manager 92xx-k5, dormakaba/access manager 92xx-k7
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
CVSS changed · 9.3
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Deferred
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
CVE published
Jan 26, 2026 · SEC-VLab

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

3 on the record

www.dormakabagroup.com/en/security-advisories
vendor-advisory, NIST National Vulnerability Database
r.sec-consult.com/dormakaba
technical-description, NIST National Vulnerability Database
r.sec-consult.com/dkaccess
third-party-advisory, NIST National Vulnerability Database

Elsewhere on this site

Dormakaba
every CVE for this vendor

Authentication
same class

CWE-306
other pages naming this weakness

Related CVEs (same products)

Critical CVE-2025-59103 Weak Default Passwords for SSH Access in dormakaba access manager Jan 26, 2026
High CVE-2025-59105 Unencrypted Flash Storage in dormakaba access manager Jan 26, 2026
Critical CVE-2025-59108 Weak Default Passwords in dormakaba access manager Jan 26, 2026
High CVE-2025-59107 Static Firmware Encryption Password in dormakaba access manager Jan 26, 2026
High CVE-2025-59104 Unlocked Bootloader in dormakaba access manager Jan 26, 2026
High CVE-2025-59106 Web Server Running with Root Privileges in dormakaba access manager Jan 26, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-59097 is "Unauthenticated SOAP API in dormakaba access manager", rated Critical. It affects Access Manager 92xx-k5 (Dormakaba); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.3 describes technical severity. EPSS 0.66% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.