# CVE-2026-45383: Memory corruption in libde265

> A heap buffer overflow in libde265 allows attackers to cause denial of service or disclose memory contents via crafted HEVC video files.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Jul 2026
- **Updated:** 22 Jul 2026
- **Also known as:** ALPINE-CVE-2026-45383, BELL-CVE-2026-45383, DEBIAN-CVE-2026-45383, ECHO-0910-d342-f525, GHSA-wg9q-ppqw-6q38, ROOT-OS-DEBIAN-11-CVE-2026-45383, UBUNTU-CVE-2026-45383

## What is CVE-2026-45383?

CVE-2026-45383 is a medium-severity memory corruption vulnerability in strukturag libde265, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-45383?


## How do I fix CVE-2026-45383?

Upgrade to a fixed version.

## Is CVE-2026-45383 being exploited?

There is no known exploitation of CVE-2026-45383 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-45383 and fix it if it is affected.

What it is: CVE-2026-45383 is a medium-severity memory corruption vulnerability in strukturag libde265, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-45383 in the wild and no public exploit code.

Affected product: strukturag libde265. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-45383/ (Markdown: https://insights.sbomify.com/CVE-2026-45383/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-45383
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-45383
- OSV: https://osv.dev/vulnerability/CVE-2026-45383

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-45383/
Summaries are generated and may contain mistakes; the official description above is the record.