CVE-2026-49346

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 74% 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: epss, secondary
7.1EG
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.1Exploit: None knownExposed: 0

A fix is available — apply it.

libde265 is an open source implementation of the h.265 video codec. Prior to version 1.1.0, a crafted H.265 bitstream with large SPS dimensions and 16-bit bit depth causes a signed integer overflow in de265_image_get_buffer() (libde265/image.cc:128). The overflow wraps the plane allocation size to a small value (~1 KB), but the subsequent fill_image() call computes the real size using size_t, writing ~4 GB into the undersized heap buffer. Version 1.1.0 patches the issue.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

June 19, 2026

Last Modified

June 26, 2026

Advisory Details (2)

Auto-updated Jun 19, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github Patch Available🟡 PoC Available

Heap buffer overflow in de265_image_get_buffer via SPS dimension integer overflow · Advisory · strukturag/libde265 · GitHub

https://github.com/strukturag/libde265/security/advisories/GHSA-vv8h-932h-7r86
github_commit Patch Available

commit 8a1b5cf212f7 (strukturag/libde265)

Patch available: strukturag/libde265 v1.1.0 (contains commit 8a1b5cf212f7)

https://github.com/strukturag/libde265/commit/8a1b5cf212f78e1c77cb46eb5d56e492a9336eb8

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibde265-examples (1.0.2-2ubuntu0.16.04.1~esm6) @ xenial2026-08-30ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
libde2651.0.11-0+deb11u1 ... 1.1.1-1 (16 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libde2651.0.11-1 ... 1.1.1-1 (10 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libde2651.0.15-11.0.15-1+deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libde2651.0.15-1, 1.0.16-1, 1.0.18-11.1.1-1—

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 56× 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.

Showing the most recent 100 of 145 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 13:47 UTCEPSS rescore
  6. 2026-09-04 05:06 UTCEPSS rescore
  7. 2026-09-02 14:12 UTCEPSS rescore
  8. 2026-09-01 13:54 UTCEPSS rescore
  9. 2026-09-01 04:40 UTCEPSS rescore
  10. 2026-08-30 20:45 UTCEG score recompute
  11. 2026-08-30 20:45 UTCVendor advisory
  12. 2026-08-30 19:17 UTCEPSS rescore
  13. 2026-08-30 01:22 UTCEPSS rescore
  14. 2026-08-28 21:41 UTCEPSS rescore
  15. 2026-08-27 14:25 UTCEPSS rescore
  16. 2026-08-26 14:46 UTCEPSS rescore
  17. 2026-08-25 13:49 UTCEPSS rescore
  18. 2026-08-25 02:42 UTCEG score recompute
  19. 2026-08-25 02:42 UTCVendor advisory
  20. 2026-08-24 13:59 UTCEG score recompute
  21. 2026-08-24 13:59 UTCVendor advisory
  22. 2026-08-24 01:08 UTCVendor advisory
  23. 2026-08-23 12:14 UTCVendor advisory
  24. 2026-08-22 23:30 UTCVendor advisory
  25. 2026-08-21 22:23 UTCVendor advisory
Show 75 more
  1. 2026-08-21 09:26 UTCEG score recompute
  2. 2026-08-21 09:26 UTCVendor advisory
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 20:43 UTCVendor advisory
  5. 2026-08-20 07:59 UTCEG score recompute
  6. 2026-08-20 07:59 UTCVendor advisory
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 05:50 UTCEG score recompute
  9. 2026-08-19 05:50 UTCVendor advisory
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-17 14:47 UTCEG score recompute
  12. 2026-08-17 14:47 UTCVendor advisory
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-17 02:04 UTCEG score recompute
  15. 2026-08-17 02:04 UTCVendor advisory
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 13:21 UTCEG score recompute
  18. 2026-08-16 13:21 UTCVendor advisory
  19. 2026-08-16 02:14 UTCEPSS rescore
  20. 2026-08-16 00:38 UTCVendor advisory
  21. 2026-08-15 11:55 UTCEG score recompute
  22. 2026-08-15 11:55 UTCVendor advisory
  23. 2026-08-15 01:30 UTCEPSS rescore
  24. 2026-08-14 23:11 UTCVendor advisory
  25. 2026-08-14 10:28 UTCEG score recompute
  26. 2026-08-14 10:28 UTCVendor advisory
  27. 2026-08-13 22:00 UTCEPSS rescore
  28. 2026-08-13 21:45 UTCVendor advisory
  29. 2026-08-13 09:02 UTCVendor advisory
  30. 2026-08-12 20:18 UTCEG score recompute
  31. 2026-08-12 20:18 UTCVendor advisory
  32. 2026-08-12 13:51 UTCEPSS rescore
  33. 2026-08-12 07:35 UTCVendor advisory
  34. 2026-08-11 18:52 UTCEG score recompute
  35. 2026-08-11 18:52 UTCVendor advisory
  36. 2026-08-11 06:09 UTCEG score recompute
  37. 2026-08-11 06:09 UTCVendor advisory
  38. 2026-08-11 00:00 UTCEPSS rescore
  39. 2026-08-10 17:26 UTCVendor advisory
  40. 2026-08-10 03:31 UTCVendor advisory
  41. 2026-08-09 14:48 UTCEG score recompute
  42. 2026-08-09 14:48 UTCVendor advisory
  43. 2026-08-09 13:46 UTCEPSS rescore
  44. 2026-08-09 02:06 UTCEG score recompute
  45. 2026-08-09 02:06 UTCVendor advisory
  46. 2026-08-08 16:37 UTCEPSS rescore
  47. 2026-08-08 13:23 UTCVendor advisory
  48. 2026-08-08 00:39 UTCEG score recompute
  49. 2026-08-08 00:39 UTCVendor advisory
  50. 2026-08-07 11:57 UTCVendor advisory
  51. 2026-08-06 23:14 UTCEG score recompute
  52. 2026-08-06 23:14 UTCVendor advisory
  53. 2026-08-06 13:47 UTCEPSS rescore
  54. 2026-08-06 10:17 UTCVendor advisory
  55. 2026-08-05 21:33 UTCEG score recompute
  56. 2026-08-05 21:33 UTCVendor advisory
  57. 2026-08-05 19:17 UTCEPSS rescore
  58. 2026-08-04 15:18 UTCEG score recompute
  59. 2026-08-04 15:18 UTCVendor advisory
  60. 2026-08-04 15:10 UTCEPSS rescore
  61. 2026-08-04 10:39 UTCEPSS rescore
  62. 2026-08-03 20:48 UTCEG score recompute
  63. 2026-08-03 20:48 UTCVendor advisory
  64. 2026-08-03 10:36 UTCEPSS rescore
  65. 2026-08-02 19:12 UTCVendor advisory
  66. 2026-08-02 06:29 UTCEG score recompute
  67. 2026-08-02 06:29 UTCVendor advisory
  68. 2026-08-02 02:27 UTCEPSS rescore
  69. 2026-08-01 17:43 UTCVendor advisory
  70. 2026-08-01 04:59 UTCEG score recompute
  71. 2026-08-01 04:16 UTCEPSS rescore
  72. 2026-07-30 22:17 UTCEG score recompute
  73. 2026-07-30 22:17 UTCVendor advisory
  74. 2026-07-30 16:28 UTCEPSS rescore
  75. 2026-07-30 03:00 UTCEG score recompute

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-49346?
CVE-2026-49346 is a high vulnerability published on June 19, 2026. libde265 is an open source implementation of the h.265 video codec. Prior to version 1.1.0, a crafted H.265 bitstream with large SPS dimensions and 16-bit bit depth causes a signed integer overflow in de265imagegetbuffer() (libde265/image.cc:128). The overflow wraps the plane allocation size to a…
When was CVE-2026-49346 disclosed?
CVE-2026-49346 was first published in the National Vulnerability Database on June 19, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49346 actively exploited?
CVE-2026-49346 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 73.2% of all scored CVEs.
What is the CVSS score of CVE-2026-49346?
CVE-2026-49346 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-49346?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49346, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-49346

Explore →

Is Your Infrastructure Affected by CVE-2026-49346?

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

Start Free Scan →Browse All CVEs