{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32603 exists.","fix":"No fix has been published for CVE-2026-32603 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-32603 is a high-severity denial of service vulnerability in sandboxie-plus Sandboxie, published on 5 May 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-32603 and fix it if it is affected.\n\nWhat it is: CVE-2026-32603 is a high-severity denial of service vulnerability in sandboxie-plus Sandboxie, published on 5 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32603 exists.\n\nAffected product: sandboxie-plus Sandboxie. 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-32603/ (Markdown: https://insights.sbomify.com/CVE-2026-32603/index.md)","id":"CVE-2026-32603","markdown":"https://insights.sbomify.com/CVE-2026-32603/index.md","name":"CVE-2026-32603","record":{"aliases":["GHSA-vvf8-cf4j-v8fv"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Windows sandbox software","requires_auth":"low_privilege","summary":"A local attacker in a Standard Sandbox can crash the Windows kernel via malformed IOCTL, causing a Blue Screen of Death.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"sandboxie","vendor":"sandboxie-plus"}],"cvss":{"score":8.2,"severity":"high","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:H","version":"4.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Sandboxie is an open source sandbox-based isolation software for Windows. In versions 1.17.2 and earlier, a local denial of service vulnerability exists in the Sandboxie kernel driver. An unprivileged process running inside a Standard Sandbox can send a malformed IOCTL to the \\Device\\SandboxieDriverApi driver, triggering an immediate kernel crash (BSOD). The vulnerability affects the Standard Sandbox configuration both with and without dropped administrator privileges, but does not affect the Security Hardened Sandbox configuration. This issue has been fixed in version 1.17.3. Users who cannot update can use the Security Hardened Sandbox configuration as a workaround.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Sandboxie kernel driver denial of service via malformed IOCTL from sandboxed process","id":"CVE-2026-32603","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Spinnaker: RCE when using gitrepo artifact types due to improper sanitization of user input on branch and paths","id":"CVE-2026-32604"},"packages":[],"prev":{"headline":"Homarr has a Race Condition in Invite Token Registration (TOCTOU)","id":"CVE-2026-32602"},"products":["Sandboxie"],"published":"2026-05-05","related":[{"cvss_score":10,"headline":"Security feature bypass in n/a","id":"CVE-2018-18748","kev_date_added":null,"published":"2018-10-28"},{"cvss_score":9.9,"headline":"Sandboxie's Integer Overflow in SbieIniServer::RC4Crypt allows sandbox escape and SYSTEM compromise","id":"CVE-2025-64721","kev_date_added":null,"published":"2025-12-11"},{"cvss_score":9.3,"headline":"Sandboxie-Plus privilege escalation via INI CRLF injection bypassing EditAdminOnly","id":"CVE-2026-34458","kev_date_added":null,"published":"2026-05-05"},{"cvss_score":9.2,"headline":"Path traversal in Sandboxie","id":"CVE-2024-49360","kev_date_added":null,"published":"2024-11-29"},{"cvss_score":8.8,"headline":"Sandboxie-Plus sandbox escape via uninitialized memory leak and stack overflow in GetRawInputDeviceInfoSlave","id":"CVE-2026-34459","kev_date_added":null,"published":"2026-05-05"},{"cvss_score":8.8,"headline":"Sandboxie-Plus NamedPipeServer OpenHandler stack overflow via unterminated server field","id":"CVE-2026-34464","kev_date_added":null,"published":"2026-05-05"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-06","vendors":["sandboxie-plus"]},"summary":"A local attacker in a Standard Sandbox can crash the Windows kernel via malformed IOCTL, causing a Blue Screen of Death.","url":"https://insights.sbomify.com/CVE-2026-32603/"}