CVE-2026-49416

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH 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.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 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(high)
EPSS
1.4%
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 34× in last 7d / 43× 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 06:00 UTCEG score recompute
  2. 2026-07-07 06:00 UTCGHSA enrichment
  3. 2026-07-06 19:00 UTCEG score recompute
  4. 2026-07-06 19:00 UTCGHSA enrichment
  5. 2026-07-06 08:00 UTCEG score recompute
  6. 2026-07-06 08:00 UTCGHSA enrichment
  7. 2026-07-05 20:58 UTCEG score recompute
  8. 2026-07-05 20:58 UTCGHSA enrichment
  9. 2026-07-05 09:57 UTCEG score recompute
  10. 2026-07-05 09:57 UTCGHSA enrichment
  11. 2026-07-05 02:30 UTCEPSS rescore
  12. 2026-07-04 22:56 UTCEG score recompute
  13. 2026-07-04 22:56 UTCGHSA enrichment
  14. 2026-07-04 11:56 UTCEG score recompute
  15. 2026-07-04 11:56 UTCGHSA enrichment
  16. 2026-07-04 06:31 UTCEPSS rescore
  17. 2026-07-04 00:56 UTCEG score recompute
  18. 2026-07-04 00:56 UTCGHSA enrichment
  19. 2026-07-03 13:56 UTCEG score recompute
  20. 2026-07-03 13:56 UTCGHSA enrichment
  21. 2026-07-03 02:57 UTCEG score recompute
  22. 2026-07-03 02:56 UTCGHSA enrichment
  23. 2026-07-02 15:55 UTCEG score recompute
  24. 2026-07-02 15:55 UTCGHSA enrichment
  25. 2026-07-02 04:55 UTCEG score recompute
Show 18 more
  1. 2026-07-02 04:55 UTCGHSA enrichment
  2. 2026-07-01 17:55 UTCEG score recompute
  3. 2026-07-01 17:55 UTCGHSA enrichment
  4. 2026-07-01 15:07 UTCEPSS rescore
  5. 2026-07-01 06:55 UTCEG score recompute
  6. 2026-07-01 06:55 UTCGHSA enrichment
  7. 2026-06-30 23:22 UTCEPSS rescore
  8. 2026-06-30 19:55 UTCEG score recompute
  9. 2026-06-30 19:55 UTCGHSA enrichment
  10. 2026-06-30 08:55 UTCEG score recompute 7.80
  11. 2026-06-30 08:55 UTCGHSA enrichment
  12. 2026-06-29 20:17 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  13. 2026-06-28 14:07 UTCEPSS rescore
  14. 2026-06-28 04:56 UTCEPSS rescore
  15. 2026-06-28 04:56 UTCEPSS rescore
  16. 2026-06-27 11:37 UTCNVD update
  17. 2026-06-27 10:00 UTCEG score recompute
  18. 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 1.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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.