CVE-2026-49337

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 75% 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
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.3Exploit: 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.0.20, a crafted sequence of H.265 NAL units causes decoder_context::read_slice_NAL() (libde265/decctx.cc:481) to attach slice headers to a finished picture object that has no active image unit, resulting in attacker-controlled unbounded heap growth. The retained headers are never freed until the picture is released, which may not happen during continuous streaming. Version 1.0.20 patches the issue.

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

Published

June 19, 2026

Last Modified

June 23, 2026

Advisory Details (2)

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

Unbounded memory accumulation via orphaned slice headers in `read_slice_NAL` · Advisory · strukturag/libde265 · GitHub

https://github.com/strukturag/libde265/security/advisories/GHSA-g5hj-rf9f-7vxm
github_commit Patch Available

commit 683cb9fa603e (strukturag/libde265)

Patch available: strukturag/libde265 v1.1.0 (contains commit 683cb9fa603e)

https://github.com/strukturag/libde265/commit/683cb9fa603e35840642f98765ab95cdb71cadf9

Patch Availability(1)

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

Frequently asked(5)

What is CVE-2026-49337?
CVE-2026-49337 is a medium vulnerability published on June 19, 2026. libde265 is an open source implementation of the h.265 video codec. Prior to version 1.0.20, a crafted sequence of H.265 NAL units causes decodercontext::readslice_NAL() (libde265/decctx.cc:481) to attach slice headers to a finished picture object that has no active image unit, resulting in…
When was CVE-2026-49337 disclosed?
CVE-2026-49337 was first published in the National Vulnerability Database on June 19, 2026, with the most recent update on June 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49337 actively exploited?
CVE-2026-49337 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 74.4% of all scored CVEs.
What is the CVSS score of CVE-2026-49337?
CVE-2026-49337 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-49337?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49337, 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-49337

Explore →

Is Your Infrastructure Affected by CVE-2026-49337?

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

Start Free Scan →Browse All CVEs