# CVE-2025-59101: Insufficient Session Management in dormakaba access manager


- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Jan 2026
- **Updated:** 26 Jan 2026
- **Also known as:** GHSA-fmc9-4f7f-vmq2

## What is CVE-2025-59101?

CVE-2025-59101 is a high-severity vulnerability in dormakaba Access Manager 92xx-k5, published on 26 Jan 2026. 

### Official description

Instead of typical session tokens or cookies, it is verified on a per-request basis if the originating IP address has once successfully logged in. As soon as an authentication request from a certain source IP is successful, the IP address is handled as authenticated. No other session information is stored. Therefore, it is possible to spoof the IP address of a logged-in user to gain access to the Access Manager web interface.

Weakness: CWE-291 (Reliance on IP Address for Authentication)

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


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

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

## Is CVE-2025-59101 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-59101 is a high-severity vulnerability in dormakaba Access Manager 92xx-k5, published on 26 Jan 2026. 
Exploitation: There is no known exploitation of CVE-2025-59101 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-59101/ (Markdown: https://insights.sbomify.com/CVE-2025-59101/index.md)
```

## Sources

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

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