# CVE-2025-59096: Weak Default Password in dormakaba Kaba exos 9300

> Attackers can gain extended admin access to dormakaba Kaba exos 9300 systems using hard-coded default passwords found in the administration software.

- **Severity:** Medium 4.6 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **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-2v5c-7g3g-hfx3

## What is CVE-2025-59096?

CVE-2025-59096 is a medium-severity vulnerability in dormakaba Kaba exos 9300, 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

The default password for the extended admin user mode in the application U9ExosAdmin.exe ("Kaba 9300 Administration") is hard-coded in multiple locations as well as documented in the locally stored user documentation.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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


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

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

## Is CVE-2025-59096 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-59096 is a medium-severity vulnerability in dormakaba Kaba exos 9300, 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-59096 in the wild and no public exploit code.

Affected product: dormakaba Kaba exos 9300. 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-59096/ (Markdown: https://insights.sbomify.com/CVE-2025-59096/index.md)
```

## Sources

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

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