# CVE-2025-59095: Hard-coded Key for PIN Encryption in dormakaba Kaba exos 9300

> Hard-coded keys in dormakaba Kaba exos 9300 allow attackers to decrypt stored user PINs, compromising access control security.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **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-56rh-rcgf-8x9j

## What is CVE-2025-59095?

CVE-2025-59095 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 program libraries (DLL) and binaries used by exos 9300 contain multiple hard-coded secrets. One notable example is the function "EncryptAndDecrypt" in the library Kaba.EXOS.common.dll. This algorithm uses a simple XOR encryption technique combined with a cryptographic key (cryptoKey) to transform each character of the input string. However, it's important to note that this implementation does not provide strong encryption and should not be considered secure for sensitive data. It's more of a custom encryption approach rather than a common algorithm used in cryptographic applications. The key itself is static and based on the founder's name of the company. The functionality is for example used to encrypt the user PINs before storing them in the MSSQL database.

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

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


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

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

## Is CVE-2025-59095 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-59095 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-59095 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-59095/ (Markdown: https://insights.sbomify.com/CVE-2025-59095/index.md)
```

## Sources

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

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