# CVE-2025-59092: Unauthenticated RPC Service in dormakaba Kaba exos 9300

> Unauthenticated RPC service allows attackers to send arbitrary status information about door contacts without prior authentication.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/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-wpq4-rhv3-hm63

## What is CVE-2025-59092?

CVE-2025-59092 is a high-severity missing authorization vulnerability in dormakaba Kaba exos 9300, published on 26 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An RPC service, which is part of exos 9300, is reachable on port 4000, run by the process FSMobilePhoneInterface.exe. This service is used for interprocess communication between services and the Kaba exos 9300 GUI, containing status information about the Access Managers. Interacting with the service does not require any authentication. Therefore, it is possible to send arbitrary status information about door contacts etc. without prior authentication.

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

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


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

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

## Is CVE-2025-59092 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-59092 is a high-severity missing authorization vulnerability in dormakaba Kaba exos 9300, 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-59092 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-59092/ (Markdown: https://insights.sbomify.com/CVE-2025-59092/index.md)
```

## Sources

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

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