# CVE-2026-8049: CVE-2026-8049

> Local attackers can exploit permissive kernel driver access to execute privileged IOCTLs, leading to privilege escalation and potential code execution.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jun 2026
- **Updated:** 18 Jun 2026
- **Also known as:** GHSA-c9xw-w9jw-mq5m

## What is CVE-2026-8049?

CVE-2026-8049 is a medium-severity vulnerability in SignalRGB kernel driver, published on 17 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In SignalRGB versions prior to 1.3.7.0, the \\.\SignalIo device object is created without an explicit SDDL security descriptor and without FILE_DEVICE_SECURE_OPEN. This results in overly permissive default access control, allowing any authenticated local user to obtain a handle to the device and issue privileged IOCTLs.

## Which versions are affected by CVE-2026-8049?


## How do I fix CVE-2026-8049?

No fix has been published for CVE-2026-8049 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-8049 being exploited?

There is no known exploitation of CVE-2026-8049 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-8049 and fix it if it is affected.

What it is: CVE-2026-8049 is a medium-severity vulnerability in SignalRGB kernel driver, published on 17 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-8049 in the wild and no public exploit code.

Affected product: SignalRGB kernel driver. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-8049/ (Markdown: https://insights.sbomify.com/CVE-2026-8049/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-8049
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-8049
- OSV: https://osv.dev/vulnerability/CVE-2026-8049

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-8049/
Summaries are generated and may contain mistakes; the official description above is the record.