CVE-2026-49417

HIGHPre-NVD 7.07.0
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.0 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 97% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cisa-adp, epss
7.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.0Exploit: NoneExposed: 0

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

Second, the audio buffer backing a mapping could be freed when the device was closed even though the mapping remained valid. The freed memory could then be reused elsewhere while still accessible through the stale mapping.

The /dev/dsp device nodes are world-accessible by default. On a system with an audio device, either issue allows an unprivileged local user to read and write kernel memory, which can be used to escalate privileges, potentially gaining full control of the affected system. At a minimum, an attacker can crash the kernel, resulting in a Denial of Service (DoS).

CVSS v3
7.0
EG Score
7.0(medium)
EPSS
2.6%
KEV
Not listed

Published

June 27, 2026

Last Modified

July 1, 2026

Advisory Details (1)

Auto-updated Jun 29, 2026
No patch confirmed yet.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 22× in last 7d / 57× 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-15 20:55 UTCEG score recompute
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 09:50 UTCEG score recompute
  5. 2026-07-14 22:56 UTCEG score recompute
  6. 2026-07-14 12:01 UTCEG score recompute
  7. 2026-07-14 01:07 UTCEG score recompute
  8. 2026-07-13 22:30 UTCEPSS rescore
  9. 2026-07-13 14:12 UTCEG score recompute
  10. 2026-07-13 06:13 UTCEPSS rescore
  11. 2026-07-13 03:16 UTCEG score recompute
  12. 2026-07-12 16:22 UTCEG score recompute
  13. 2026-07-12 05:46 UTCEPSS rescore
  14. 2026-07-12 05:28 UTCEG score recompute
  15. 2026-07-11 18:32 UTCEG score recompute
  16. 2026-07-11 08:27 UTCEPSS rescore
  17. 2026-07-11 07:38 UTCEG score recompute
  18. 2026-07-10 20:41 UTCEG score recompute
  19. 2026-07-10 09:47 UTCEG score recompute
  20. 2026-07-09 22:45 UTCEG score recompute
  21. 2026-07-09 19:10 UTCEPSS rescore
  22. 2026-07-09 11:50 UTCEG score recompute
  23. 2026-07-09 00:55 UTCEG score recompute
  24. 2026-07-08 15:16 UTCEPSS rescore
  25. 2026-07-08 14:01 UTCEG score recompute
Show 32 more
  1. 2026-07-08 03:04 UTCEG score recompute
  2. 2026-07-07 16:08 UTCEG score recompute
  3. 2026-07-07 13:46 UTCEPSS rescore
  4. 2026-07-07 05:06 UTCEG score recompute
  5. 2026-07-06 18:10 UTCEG score recompute
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 07:14 UTCEG score recompute
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 20:20 UTCEG score recompute
  10. 2026-07-05 09:25 UTCEG score recompute
  11. 2026-07-04 22:31 UTCEG score recompute
  12. 2026-07-04 11:36 UTCEG score recompute
  13. 2026-07-04 00:41 UTCEG score recompute
  14. 2026-07-03 13:43 UTCEG score recompute
  15. 2026-07-03 02:48 UTCEG score recompute
  16. 2026-07-02 15:53 UTCEG score recompute
  17. 2026-07-02 04:58 UTCEG score recompute
  18. 2026-07-01 18:03 UTCEG score recompute
  19. 2026-07-01 15:07 UTCEPSS rescore
  20. 2026-07-01 07:09 UTCEG score recompute
  21. 2026-06-30 23:22 UTCEPSS rescore
  22. 2026-06-30 20:14 UTCEG score recompute
  23. 2026-06-30 09:20 UTCEG score recompute 7.00
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-29 14:06 UTCEPSS rescore
  26. 2026-06-29 13:32 UTCMITRE cvelistV5CVSS v3 → 7 · severity → HIGH
  27. 2026-06-28 14:07 UTCEPSS rescore
  28. 2026-06-28 04:56 UTCEPSS rescore
  29. 2026-06-28 04:56 UTCEPSS rescore
  30. 2026-06-27 09:36 UTCNVD update
  31. 2026-06-27 09:15 UTCEG score recompute
  32. 2026-06-27 09:14 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-49417?
CVE-2026-49417 is a high vulnerability published on June 27, 2026. Second, the audio buffer backing a mapping could be freed when the device was closed even though the mapping remained valid. The freed memory could then be reused elsewhere while still accessible through the stale mapping. The /dev/dsp device nodes are world-accessible by default. On a system with…
When was CVE-2026-49417 disclosed?
CVE-2026-49417 was first published in the National Vulnerability Database on June 27, 2026, with the most recent update on July 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49417 actively exploited?
CVE-2026-49417 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-49417?
CVE-2026-49417 has a CVSS v3.1 base score of 7.0 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-49417?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49417, 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-49417

Explore →

Is Your Infrastructure Affected by CVE-2026-49417?

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