CVE-2026-8049

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory published 2026-06-18. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.3
EG Score
5.3(high)
EPSS
0.5%
KEV
Not listed

Published

June 17, 2026

Last Modified

June 22, 2026

Advisory Details (1)

Auto-updated Jun 18, 2026
No patch confirmed yet. Sources: cert.
cert

VU#380058 - SignalRGB kernel driver contains improper access control and IOCTL vulnerabilities

https://kb.cert.org/vuls/id/380058

Vendor Advisories for CVE-2026-8049(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 22× in last 7d / 51× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 05:28 UTCEG score recompute
  2. 2026-07-07 05:28 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 03:34 UTCEG score recompute
  6. 2026-07-06 03:34 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 02:31 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-05 01:45 UTCEG score recompute
  12. 2026-07-05 01:45 UTCGHSA enrichment
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-04 06:31 UTCEPSS rescore
  15. 2026-07-03 23:58 UTCEG score recompute
  16. 2026-07-03 23:58 UTCGHSA enrichment
  17. 2026-07-02 22:11 UTCEG score recompute
  18. 2026-07-02 22:11 UTCGHSA enrichment
  19. 2026-07-01 20:24 UTCEG score recompute
  20. 2026-07-01 20:24 UTCGHSA enrichment
  21. 2026-06-30 18:38 UTCEG score recompute
  22. 2026-06-30 18:38 UTCGHSA enrichment
  23. 2026-06-29 16:50 UTCEG score recompute
  24. 2026-06-29 16:50 UTCGHSA enrichment
  25. 2026-06-28 15:00 UTCEG score recompute
Show 26 more
  1. 2026-06-28 15:00 UTCGHSA enrichment
  2. 2026-06-28 14:07 UTCEPSS rescore
  3. 2026-06-28 04:56 UTCEPSS rescore
  4. 2026-06-27 13:13 UTCEG score recompute
  5. 2026-06-27 13:13 UTCGHSA enrichment
  6. 2026-06-27 03:08 UTCEPSS rescore
  7. 2026-06-26 11:27 UTCEG score recompute
  8. 2026-06-26 11:27 UTCGHSA enrichment
  9. 2026-06-25 13:50 UTCEPSS rescore
  10. 2026-06-25 05:16 UTCEG score recompute
  11. 2026-06-25 05:16 UTCGHSA enrichment
  12. 2026-06-24 14:05 UTCEPSS rescore
  13. 2026-06-24 03:30 UTCEG score recompute
  14. 2026-06-24 03:29 UTCGHSA enrichment
  15. 2026-06-23 01:42 UTCEG score recompute
  16. 2026-06-23 01:42 UTCGHSA enrichment
  17. 2026-06-21 23:54 UTCEG score recompute
  18. 2026-06-21 23:54 UTCGHSA enrichment
  19. 2026-06-21 14:56 UTCEPSS rescore
  20. 2026-06-20 22:04 UTCEG score recompute▲ 5.30
  21. 2026-06-20 22:04 UTCGHSA enrichment
  22. 2026-06-19 19:26 UTCEPSS rescore
  23. 2026-06-18 17:52 UTCEPSS rescore
  24. 2026-06-18 15:53 UTCNVD updateCVSS v3 → 5.3 · severity → MEDIUM
  25. 2026-06-17 23:17 UTCEG score recompute
  26. 2026-06-17 23:16 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-8049?
CVE-2026-8049 is a medium vulnerability published on June 17, 2026. In SignalRGB versions prior to 1.3.7.0, the \\.\SignalIo device object is created without an explicit SDDL security descriptor and without FILEDEVICESECURE_OPEN. This results in overly permissive default access control, allowing any authenticated local user to obtain a handle to the device and…
When was CVE-2026-8049 disclosed?
CVE-2026-8049 was first published in the National Vulnerability Database on June 17, 2026, with the most recent update on June 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-8049 actively exploited?
CVE-2026-8049 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-8049?
CVE-2026-8049 has a CVSS v3.1 base score of 5.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-8049?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-8049, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-8049

Explore →

Is Your Infrastructure Affected by CVE-2026-8049?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs