libde265 is an open source implementation of the h.265 video codec. Versions prior to 1.0.19 have a heap buffer overflow (out-of-bounds READ) exists in decoder_context::decode_slice_unit_WPP() in libde265/decctx.cc. When decoding a WPP (Wavefront Parallel Processing) HEVC slice, ctbAddrRS is computed as ctbRow * ctbsWidth inside the entry-point loop. If the PPS/SPS headers are crafted so that this value exceeds pps.CtbAddrRStoTS.size(), the subsequent array access pps.CtbAddrRStoTS[ctbAddrRS] reads past the end of the allocated vector, triggering a heap-buffer-overflow confirmed by AddressSanitizer. Version 1.0.19 patches the issue.
CVE-2026-45383
This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 65% 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).
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 6.9
- EG Score
- 6.9(medium)
- EG Risk
- 46(Track)EG Risk 46/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 computedSeverity69% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 35%
- KEV
- Not listed
Published
July 21, 2026
Last Modified
July 23, 2026
Advisory Details (1)
Auto-updated Jul 21, 2026Heap buffer overflow (OOB read) in decode_slice_unit_WPP() via out-of-bounds CtbAddrRStoTS access — libde265 <= v1.0.18 · Advisory · strukturag/libde265 · GitHub
https://github.com/strukturag/libde265/security/advisories/GHSA-wg9q-ppqw-6q38Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | libde265-examples (1.0.2-2ubuntu0.18.04.1~esm6) @ bionic | 2026-08-30 | ubuntu |
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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libde265 | 1.0.11-0+deb11u1 ... 1.1.1-1 (16 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libde265 | 1.0.11-1 ... 1.1.1-1 (10 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libde265 | 1.0.15-1 | 1.0.15-1+deb13u1 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libde265 | 1.0.15-1, 1.0.16-1, 1.0.18-1 | 1.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 17× in last 7d / 78× 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.
- 2026-08-30 02:10 UTCEG score recompute
- 2026-08-30 02:10 UTCVendor advisory
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-28 04:29 UTCEG score recompute
- 2026-08-28 04:29 UTCVendor advisory
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 02:05 UTCEG score recompute
- 2026-08-27 02:05 UTCVendor advisory
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 23:42 UTCEG score recompute
- 2026-08-25 23:42 UTCVendor advisory
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 21:08 UTCEG score recompute
- 2026-08-24 21:08 UTCVendor advisory
- 2026-08-23 18:44 UTCEG score recompute
- 2026-08-23 18:44 UTCVendor advisory
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 16:22 UTCEG score recompute
- 2026-08-22 16:22 UTCVendor advisory
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 13:59 UTCEG score recompute
- 2026-08-21 13:59 UTCVendor advisory
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 11:34 UTCEG score recompute
Show 75 moreShow fewer
- 2026-08-20 11:34 UTCVendor advisory
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 09:08 UTCEG score recompute
- 2026-08-19 09:08 UTCVendor advisory
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 06:41 UTCEG score recompute
- 2026-08-18 06:41 UTCVendor advisory
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 04:18 UTCEG score recompute
- 2026-08-17 04:18 UTCVendor advisory
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-16 01:55 UTCEG score recompute
- 2026-08-16 01:55 UTCVendor advisory
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 23:32 UTCEG score recompute
- 2026-08-14 23:32 UTCVendor advisory
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 21:09 UTCVendor advisory
- 2026-08-12 18:41 UTCEG score recompute
- 2026-08-12 18:41 UTCVendor advisory
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-11 16:18 UTCEG score recompute
- 2026-08-11 16:18 UTCVendor advisory
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 13:56 UTCEG score recompute
- 2026-08-10 13:56 UTCVendor advisory
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 11:33 UTCEG score recompute
- 2026-08-09 11:33 UTCVendor advisory
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 09:08 UTCEG score recompute
- 2026-08-08 09:08 UTCVendor advisory
- 2026-08-07 06:45 UTCEG score recompute
- 2026-08-07 06:45 UTCVendor advisory
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 04:22 UTCEG score recompute
- 2026-08-06 04:22 UTCVendor advisory
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 01:59 UTCEG score recompute
- 2026-08-05 01:59 UTCVendor advisory
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:38 UTCEPSS rescore
- 2026-08-03 23:36 UTCEG score recompute
- 2026-08-03 23:36 UTCVendor advisory
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 21:14 UTCEG score recompute
- 2026-08-02 21:14 UTCVendor advisory
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 18:51 UTCEG score recompute
- 2026-08-01 18:51 UTCVendor advisory
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-31 16:28 UTCEG score recompute
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 13:57 UTCEG score recompute
- 2026-07-30 13:57 UTCVendor advisory
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-29 11:33 UTCEG score recompute
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-28 09:09 UTCEG score recompute
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-27 06:45 UTCEG score recompute
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 04:18 UTCEG score recompute
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:16 UTCEG score recompute
- 2026-07-22 22:57 UTCEG score recompute
- 2026-07-22 22:57 UTCVendor advisory
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 21:22 UTCEG score recompute
- 2026-07-21 21:10 UTCEG score recompute
- 2026-07-21 21:08 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-45383?
When was CVE-2026-45383 disclosed?
Is CVE-2026-45383 actively exploited?
What is the CVSS score of CVE-2026-45383?
How do I remediate CVE-2026-45383?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45383
Is Your Infrastructure Affected by CVE-2026-45383?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.