{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-111732 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-111732 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-111732 is a critical vulnerability in RT-Labs P-Net, published on 29 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-111732 and fix it if it is affected.\n\nWhat it is: CVE-2026-111732 is a critical vulnerability in RT-Labs P-Net, published on 29 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-111732 in the wild and no public exploit code.\n\nAffected product: RT-Labs P-Net. 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-111732/ (Markdown: https://insights.sbomify.com/CVE-2026-111732/index.md)","id":"CVE-2026-111732","markdown":"https://insights.sbomify.com/CVE-2026-111732/index.md","name":"CVE-2026-111732","record":{"aliases":["GHSA-h967-v272-9m8r"],"analysis":null,"analysis_generated_by":null,"assigner":"rt-labs","cpe":[],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"P-Net before 1.0.3, when built with PNET_OPTION_AR_VENDOR_BLOCKS enabled, parses a data length from a field of the ARVendorBlock request that is not part of the block definition and uses it as the number of bytes to copy into a fixed-size buffer, without comparing it with the buffer size or the block length. A crafted Connect request causes an out-of-bounds write. This can lead to a crash (denial of service) or potentially arbitrary code execution.\n\nThis option is disabled by default.","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":"Out-of-bounds write when parsing AR Vendor Block requests","id":"CVE-2026-111732","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"NULL pointer dereference on implicit read of AR specific record index","id":"CVE-2026-111733"},"packages":[],"prev":{"headline":"Infinite loop when reading PDPortDataCheck record of subslot 0","id":"CVE-2026-111731"},"products":["P-Net"],"published":"2026-10-29","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-29","vendors":["RT-Labs"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-111732/"}