{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-105960 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-105960 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-105960 is a medium-severity vulnerability in HMS Networks PCAN Windows CAN device drivers, published on 20 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-105960 and fix it if it is affected.\n\nWhat it is: CVE-2026-105960 is a medium-severity vulnerability in HMS Networks PCAN Windows CAN device drivers, published on 20 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-105960 in the wild and no public exploit code.\n\nAffected product: HMS Networks PCAN Windows CAN device drivers. 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-105960/ (Markdown: https://insights.sbomify.com/CVE-2026-105960/index.md)","id":"CVE-2026-105960","markdown":"https://insights.sbomify.com/CVE-2026-105960/index.md","name":"CVE-2026-105960","record":{"aliases":["GHSA-xmr7-q6v2-429j"],"analysis":null,"analysis_generated_by":null,"assigner":"icscert","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:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-130","name":"Improper Handling of Length Parameter Inconsistency"}],"description":"PEAK-System PCAN contains a vulnerable operation involving a variable-length receive-record copy. The driver uses a requested or queued record count without sufficiently capping the copy to the actual caller-supplied output length.","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":"HMS Networks PEAK-System PCAN Windows drivers Improper Handling of Length Parameter Inconsistency","id":"CVE-2026-105960","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Secret key base exposed in stack trace arguments on wrong-typed Plug.Crypto arguments","id":"CVE-2026-105963"},"packages":[],"prev":{"headline":"Spice-server: spice: heap buffer overflow via glz dictionary max_encoders integer truncation","id":"CVE-2026-105959"},"products":["PCAN Windows CAN device drivers","PEAK-System Device Driver Setup"],"published":"2026-10-20","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-20","vendors":["HMS Networks"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-105960/"}