# CVE-2026-49346: libde265 has a heap buffer overflow in de265_image_get_buffer via SPS dimension integer overflow

> A crafted H.265 bitstream triggers an integer overflow leading to a heap buffer overflow, allowing attackers to execute arbitrary code or crash the application.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 19 Jun 2026
- **Updated:** 22 Jun 2026
- **Also known as:** ALPINE-CVE-2026-49346, BELL-CVE-2026-49346, DEBIAN-CVE-2026-49346, ECHO-7756-d9d5-6fc4, GHSA-vv8h-932h-7r86, JLSEC-2026-790, MINI-gm5r-6m7r-9457, ROOT-OS-DEBIAN-11-CVE-2026-49346, UBUNTU-CVE-2026-49346

## What is CVE-2026-49346?

CVE-2026-49346 is a high-severity vulnerability in Struktur Libde265, published on 19 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Struktur Libde265.

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

Upgrade to a fixed version.

## Is CVE-2026-49346 being exploited?

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

## Other vulnerabilities in Struktur Libde265

- [CVE-2023-49465](https://insights.sbomify.com/CVE-2023-49465/): Memory corruption in n/a (high 8.8)
- [CVE-2023-49467](https://insights.sbomify.com/CVE-2023-49467/): Memory corruption in n/a (high 8.8)
- [CVE-2023-49468](https://insights.sbomify.com/CVE-2023-49468/): Memory corruption in n/a (high 8.8)
- [CVE-2023-27103](https://insights.sbomify.com/CVE-2023-27103/): Memory corruption in n/a (high 8.8)
- [CVE-2026-33164](https://insights.sbomify.com/CVE-2026-33164/): NULL Pointer Dereference in libde265 (high 8.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-49346 is a high-severity vulnerability in Struktur Libde265, published on 19 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49346 exists.

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

## Sources

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

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