{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-8050 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-8050 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-8050 is a high-severity vulnerability in SignalRGB kernel driver, published on 17 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-8050 and fix it if it is affected.\n\nWhat it is: CVE-2026-8050 is a high-severity vulnerability in SignalRGB kernel driver, published on 17 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-8050 in the wild and no public exploit code.\n\nAffected product: SignalRGB kernel 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-8050/ (Markdown: https://insights.sbomify.com/CVE-2026-8050/index.md)","id":"CVE-2026-8050","markdown":"https://insights.sbomify.com/CVE-2026-8050/index.md","name":"CVE-2026-8050","record":{"aliases":["GHSA-wm74-h69m-r7vv"],"analysis":{"component_type":"kernel","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"SignalRGB kernel driver","requires_auth":"none","summary":"A local attacker can cause a kernel crash in SignalRGB by sending an IOCTL with an empty buffer, leading to denial of service.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"certcc","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[],"description":"In SignalRGB versions prior to 1.3.7.0, seven of the thirteen IOCTL handlers dereference the SystemBuffer pointer without first verifying that it is non-NULL. Sending an IOCTL with an empty input buffer causes a NULL pointer dereference, resulting in a kernel crash.","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":"CVE-2026-8050","id":"CVE-2026-8050","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Command injection in Virtual Traffic Manager","id":"CVE-2026-8051"},"packages":[],"prev":{"headline":"CVE-2026-8049","id":"CVE-2026-8049"},"products":["SignalRGB kernel driver"],"published":"2026-06-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-18","vendors":["SignalRGB"]},"summary":"A local attacker can cause a kernel crash in SignalRGB by sending an IOCTL with an empty buffer, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-8050/"}