# CVE-2026-45382: libde265 has a heap-buffer-overflow READ in decode_slice_unit_tiles via unvalidated PPS tile geometry

> A heap-buffer-overflow in libde265 allows attackers to cause denial of service or disclose memory via malformed 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:** 23 Jul 2026
- **Also known as:** ALPINE-CVE-2026-45382, BELL-CVE-2026-45382, DEBIAN-CVE-2026-45382, ECHO-6d7b-247d-24f3, GHSA-hwhx-x2mq-ccr9, ROOT-OS-DEBIAN-11-CVE-2026-45382, UBUNTU-CVE-2026-45382

## What is CVE-2026-45382?

CVE-2026-45382 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. Prior to version 1.0.19, `decoder_context::decode_slice_unit_tiles` (libde265/decctx.cc:920) reads `pps.CtbAddrRStoTS[ctbAddrRS]` at line 966 where `ctbAddrRS = ctbY * ctbsWidth + ctbX` is computed from PPS-supplied `colBd[]`/`rowBd[]` arrays without validating the result against `CtbAddrRStoTS.size() == sps->PicSizeInCtbsY`. A malformed PPS that passes `set_derived_values` but encodes geometry inconsistent with the SPS produces a `ctbAddrRS` past the allocation, causing a 4-byte heap-buffer-overflow READ. Version 1.0.19 fixes the issue.

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

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


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

Upgrade to a fixed version.

## Is CVE-2026-45382 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45382 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45382 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45382 exists.

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-45382/ (Markdown: https://insights.sbomify.com/CVE-2026-45382/index.md)
```

## Sources

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

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