# CVE-2025-59103: Weak Default Passwords for SSH Access in dormakaba access manager

> Attackers can gain SSH access to dormakaba Access Manager devices using hardcoded or weak default passwords, leading to full system compromise.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:P/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jan 2026
- **Updated:** 26 Jan 2026
- **Also known as:** GHSA-cm8m-44xc-f932

## What is CVE-2025-59103?

CVE-2025-59103 is a critical vulnerability in dormakaba Access Manager 92xx-k5, published on 26 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Access Manager 92xx in hardware revision K7 is based on Linux instead of Windows CE embedded in older hardware revisions. In this new hardware revision it was noticed that an SSH service is exposed on port 22. By analyzing the firmware of the devices, it was noticed that there are two users with hardcoded and weak passwords that can be used to access the devices via SSH. The passwords can be also guessed very easily. The password of at least one user is set to a random value after the first deployment, with the restriction that the password is only randomized if the configured date is prior to 2022. Therefore, under certain circumstances, the passwords are not randomized. For example, if the clock is never set on the device, the battery of the clock module has been changed, the Access Manager has been factory reset and has not received a time yet.

Weakness: CWE-1391 (Use of Weak Credentials)

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


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

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

## Is CVE-2025-59103 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-59103 is a critical vulnerability in dormakaba Access Manager 92xx-k5, published on 26 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-59103 in the wild and no public exploit code.

Affected product: dormakaba Access Manager 92xx-k5. 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-59103/ (Markdown: https://insights.sbomify.com/CVE-2025-59103/index.md)
```

## Sources

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

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