# CVE-2025-59104: Unlocked Bootloader in dormakaba access manager

> Physical attackers can solder debug leads to bypass bootloader restrictions and gain root shell access on dormakaba access managers.

- **Severity:** High 7.0 (`CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jan 2026
- **Updated:** 26 Jan 2026
- **Also known as:** GHSA-82wq-479r-x8x9

## What is CVE-2025-59104?

CVE-2025-59104 is a high-severity vulnerability in dormakaba Access Manager 92xx-k7, published on 26 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

With physical access to the device and enough time an attacker is able to solder test leads to the debug footprint (or use the 6-Pin tag-connect cable). Thus, the attacker gains access to the bootloader, where the kernel command line can be changed. An attacker is able to gain a root shell through this vulnerability.

Weakness: CWE-1234 (Hardware Internal or Debug Modes Allow Override of Locks)

## Which versions are affected by CVE-2025-59104?


## How do I fix CVE-2025-59104?

No fix has been published for CVE-2025-59104 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-59104 being exploited?

There is no known exploitation of CVE-2025-59104 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59104 and fix it if it is affected.

What it is: CVE-2025-59104 is a high-severity vulnerability in dormakaba Access Manager 92xx-k7, published on 26 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-59104 in the wild and no public exploit code.

Affected product: dormakaba Access Manager 92xx-k7. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-59104/ (Markdown: https://insights.sbomify.com/CVE-2025-59104/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-59104
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-59104
- OSV: https://osv.dev/vulnerability/CVE-2025-59104

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-59104/
Summaries are generated and may contain mistakes; the official description above is the record.