{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-59109 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-59109 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-59109 is a medium-severity vulnerability in dormakaba registration unit 9002, published on 26 Jan 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-59109 and fix it if it is affected.\n\nWhat it is: CVE-2025-59109 is a medium-severity vulnerability in dormakaba registration unit 9002, published on 26 Jan 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-59109 in the wild and no public exploit code.\n\nAffected product: dormakaba registration unit 9002. 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-59109/ (Markdown: https://insights.sbomify.com/CVE-2025-59109/index.md)","id":"CVE-2025-59109","markdown":"https://insights.sbomify.com/CVE-2025-59109/index.md","name":"CVE-2025-59109","record":{"aliases":["GHSA-4m2m-3rvh-cp5p"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"PIN pad unit","requires_auth":"none","summary":"An attacker with physical access can connect to the exposed UART interface to exfiltrate sensitive PIN data entered on the device.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"SEC-VLab","cpe":[],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-1295","name":"Debug Messages Revealing Unnecessary Information"}],"description":"The dormakaba registration units 9002 (PIN Pad Units) have an exposed UART header on the backside. The PIN pad is sending every button press to the UART interface. An attacker can use the interface to exfiltrate PINs. As the devices are explicitly built as Plug-and-Play to be easily replaced, an attacker is easily able to remove the device, install a hardware implant which connects to the UART and exfiltrates the data exposed via UART to another system (e.g. via WiFi).","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":"UART Leaking Sensitive Data in dormakaba registration unit 9002","id":"CVE-2025-59109","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":"Cross-Site Request Forgery in Windu CMS","id":"CVE-2025-59110"},"packages":[],"prev":{"headline":"Weak Default Passwords in dormakaba access manager","id":"CVE-2025-59108"},"products":["dormakaba registration unit 9002"],"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":"partial"},"state":"PUBLISHED","updated":"2026-03-03","vendors":["dormakaba"]},"summary":"An attacker with physical access can connect to the exposed UART interface to exfiltrate sensitive PIN data entered on the device.","url":"https://insights.sbomify.com/CVE-2025-59109/"}