CVE-2026-49416

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-27. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

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

The CONS_HISTORY ioctl handler did not adequately validate the requested history size. A large value caused an integer overflow in the buffer size calculation, resulting in a heap allocation smaller than expected. Subsequent initialization of the buffer wrote beyond the end of the allocation.

An unprivileged local user with access to a vt(4) device can trigger an out-of-bounds write in the kernel, potentially escalating privileges.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

June 27, 2026

Last Modified

July 1, 2026

Advisory Details (1)

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

Vendor Advisories for CVE-2026-49416(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-49416?
CVE-2026-49416 is a high vulnerability published on June 27, 2026. The CONS_HISTORY ioctl handler did not adequately validate the requested history size. A large value caused an integer overflow in the buffer size calculation, resulting in a heap allocation smaller than expected. Subsequent initialization of the buffer wrote beyond the end of the allocation. An…
When was CVE-2026-49416 disclosed?
CVE-2026-49416 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-49416 actively exploited?
CVE-2026-49416 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.7% of all scored CVEs.
What is the CVSS score of CVE-2026-49416?
CVE-2026-49416 has a CVSS v3.1 base score of 7.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-49416?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49416, 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-49416

Explore →

Is Your Infrastructure Affected by CVE-2026-49416?

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