{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-56129 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-56129 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-56129 is a medium-severity missing authorization vulnerability in Dynabook Inc. Generic IO \u0026 Memory Access driver, published on 25 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-56129 and fix it if it is affected.\n\nWhat it is: CVE-2026-56129 is a medium-severity missing authorization vulnerability in Dynabook Inc. Generic IO \u0026 Memory Access driver, published on 25 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-56129 in the wild and no public exploit code.\n\nAffected product: Dynabook Inc. Generic IO \u0026 Memory Access driver. 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-2026-56129/ (Markdown: https://insights.sbomify.com/CVE-2026-56129/index.md)","id":"CVE-2026-56129","markdown":"https://insights.sbomify.com/CVE-2026-56129/index.md","name":"CVE-2026-56129","record":{"aliases":["GHSA-62xh-mjg9-8qhv"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["privilege_escalation","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Generic IO driver","requires_auth":"low_privilege","summary":"A local attacker can access physical memory via the Generic IO driver due to insufficient access control, leading to privilege escalation.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jpcert","cpe":[],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-782","name":"Exposed IOCTL with Insufficient Access Control"}],"description":"Generic IO \u0026 Memory Access driver for PCs provided by TOSHIBA CORPORATION and Dynabook Inc. exposes its IOCTL with insufficient access control. A logged-in user with no administrative privilege may access physical memory.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-05-15","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-05-15T21:23:34Z","kind":"github_poc","ref":"https://github.com/valium007/CVE-2026-56129","stars":0,"title":"Toshiba Qiomem.sys vulnerable driver POC (CVE-2026-56129)"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Missing authorization in Generic IO \u0026 Memory Access driver","id":"CVE-2026-56129","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Apache Shiro: Remember-me cookie isn't checked for expiry on the server","id":"CVE-2026-56130"},"packages":[],"prev":{"headline":"pfSense Plus \u003c 26.07 / CE \u003c 2.9.0 Stored XSS via firewall_schedule_edit.php","id":"CVE-2026-56128"},"products":["Generic IO \u0026 Memory Access driver"],"published":"2026-06-25","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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-25","vendors":["Dynabook Inc.","TOSHIBA CORPORATION"]},"summary":"A local attacker can access physical memory via the Generic IO driver due to insufficient access control, leading to privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-56129/"}