{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-59101 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-59101 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-59101 is a high-severity vulnerability in dormakaba Access Manager 92xx-k5, published on 26 Jan 2026."},"fix_prompt":"Check this codebase for CVE-2025-59101 and fix it if it is affected.\n\nWhat it is: CVE-2025-59101 is a high-severity vulnerability in dormakaba Access Manager 92xx-k5, published on 26 Jan 2026. \nExploitation: There is no known exploitation of CVE-2025-59101 in the wild and no public exploit code.\n\nAffected product: dormakaba Access Manager 92xx-k5. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-59101/ (Markdown: https://insights.sbomify.com/CVE-2025-59101/index.md)","id":"CVE-2025-59101","markdown":"https://insights.sbomify.com/CVE-2025-59101/index.md","name":"CVE-2025-59101","record":{"aliases":["GHSA-fmc9-4f7f-vmq2"],"analysis":null,"analysis_generated_by":null,"assigner":"SEC-VLab","cpe":[],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-291","name":"Reliance on IP Address for Authentication"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Insufficient Session Management in dormakaba access manager","id":"CVE-2025-59101","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Secrets Stored in Plaintext in Database in dormakaba access manager","id":"CVE-2025-59102"},"packages":[],"prev":{"headline":"Unauthenticated Access to the SQLite Database in dormakaba access manager","id":"CVE-2025-59100"},"products":["Access Manager 92xx-k5","Access Manager 92xx-k7"],"published":"2026-01-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-01-26","vendors":["dormakaba"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2025-59101/"}