{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-59098 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-59098 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-59098 is a high-severity vulnerability in dormakaba Access Manager 92xx-k5, published on 26 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-59098 and fix it if it is affected.\n\nWhat it is: CVE-2025-59098 is a high-severity vulnerability in dormakaba Access Manager 92xx-k5, published on 26 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-59098 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-59098/ (Markdown: https://insights.sbomify.com/CVE-2025-59098/index.md)","id":"CVE-2025-59098","markdown":"https://insights.sbomify.com/CVE-2025-59098/index.md","name":"CVE-2025-59098","record":{"aliases":["GHSA-p5p6-g8q2-vx84"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Access control system","requires_auth":"none","summary":"Unauthenticated attackers can access a debug TCP socket to retrieve sensitive data, including PINs and card IDs, from dormakaba access managers.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"SEC-VLab","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-497","name":"Exposure of Sensitive System Information to an Unauthorized Control Sphere"}],"description":"The Access Manager is offering a trace functionality to debug errors and issues with the device. The trace functionality is implemented as a simple TCP socket. A tool called TraceClient.exe, provided by dormakaba via the Access Manager web interface, is used to connect to the socket and receive debug information. The data is permanently broadcasted on the TCP socket. The socket can be accessed without any authentication or encryption. \n\nThe transmitted data is based on the set verbosity level. The verbosity level can be set using the http(s) endpoint with the service interface password or with the guessable identifier of the device via the SOAP interface.\n\nThe transmitted data contains sensitive data like the Card ID as well as all button presses on Registration units. This allows an attacker with network level access to retrieve all entered PINs on a registration unit.","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":"Trace Functionality Leaking Sensitive Data in dormakaba access manager","id":"CVE-2025-59098","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Unauthenticated Path Traversal in dormakaba access manager","id":"CVE-2025-59099"},"packages":[],"prev":{"headline":"Unauthenticated SOAP API in dormakaba access manager","id":"CVE-2025-59097"},"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-26","vendors":["dormakaba"]},"summary":"Unauthenticated attackers can access a debug TCP socket to retrieve sensitive data, including PINs and card IDs, from dormakaba access managers.","url":"https://insights.sbomify.com/CVE-2025-59098/"}