VulnerabilityPublished 26 Jan 2026Updated 3 Mar 2026

CVE-2025-59109: dormakaba registration unit 9002 · Debug Messages Revealing Unnecessary Information

Affects dormakaba registration unit 9002Source CVE Database V5

Not known to be exploited · CVSS 5.1 Medium : upgrade to SW0039 when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score

5.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in SW0039

CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector: Physical
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: Active
Vulnerable system confidentiality: High
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable system. Physical interaction may be brief (e.g., evil maid attack) or persistent.
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: Active: Successful exploitation of this vulnerability requires a targeted user to perform specific, conscious interactions with the vulnerable system and the attacker’s payload, or the user’s interactions would actively subvert protection mechanisms which would lead to exploitation of the vulnerability.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade dormakaba registration unit 9002 to SW0039.

Affected software

Product	Affected	Fixed in
dormakabadormakaba registration unit 9002	Affected <SW0039	Fixed in SW0039

AI-suggested

Enforce strict physical security controls around PIN pad devices to prevent unauthorized removal or tampering, including surveillance and tamper-evident seals.
Regularly inspect devices for signs of hardware implants or unauthorized modifications.
Restrict access to areas where PIN pads are installed to trusted personnel only.
Coordinate with dormakaba to obtain firmware updates beyond version SW0039 that address this vulnerability and apply them promptly.
Consider deploying additional authentication factors or alternative input methods that do not expose sensitive data via hardware interfaces.
Implement network monitoring to detect unusual wireless signals near PIN pad locations that could indicate data exfiltration attempts.
Educate staff on the risks of physical device tampering and encourage reporting of suspicious activity.
For new deployments, evaluate alternative devices that do not expose debug interfaces or sensitive input data.
If possible, disable or physically block access to the UART header on existing devices to prevent hardware implants.
Maintain an inventory of all PIN pad devices and their firmware versions to ensure timely vulnerability management.

Description

The dormakaba registration units 9002 (PIN Pad Units) have an exposed UART header on the backside. The PIN pad is sending every button press to the UART interface. An attacker can use the interface to exfiltrate PINs. As the devices are explicitly built as Plug-and-Play to be easily replaced, an attacker is easily able to remove the device, install a hardware implant which connects to the UART and exfiltrates the data exposed via UART to another system (e.g.via WiFi).

Impact

The primary impact is the compromise of PIN confidentiality, which can lead to unauthorized physical or logical access if attackers obtain valid credentials. Organizations using dormakaba registration unit 9002 PIN pads for access control, time attendance, or secure authentication may face increased risk of insider threats or external attackers gaining entry. The ease of physical removal and implant installation means that facilities with insufficient physical security controls are particularly vulnerable. While the vulnerability does not affect system integrity or availability directly, the loss of credential confidentiality can cascade into broader security breaches. The attack requires physical access, so environments with high foot traffic or less controlled hardware access points are at greater risk. The absence of known exploits in the wild suggests this is a latent threat, but the medium CVSS score reflects the realistic potential for exploitation in targeted attacks. The lack of firmware patches increases exposure duration. Organizations may also face compliance and reputational risks if PIN data is leaked.

CWE-1295Debug Messages Revealing Unnecessary Information (opens in a new tab)
Base weakness
The product fails to adequately prevent the revealing of unnecessary and potentially sensitive system information within debugging messages.
Implementation
Ensure that a debug message does not reveal any unnecessary information during the debug process for the intended response.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Exploit Non-Production Interfaces (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Mar 2026, 18:33 UTC

WeaknessesCWE-1295

Technical details

References

Community reviews

Related threats