Quick answers
- Is CVE-2026-49346 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-49346 being exploited in the wild.
- How severe is CVE-2026-49346?
- High severity, with a CVSS score of 7.1, published 19 June 2026.
- Which products and versions are affected?
- struktur AG Libde265 < 1.1.0.
- Is there a fix for CVE-2026-49346?
- A patch was published on 2026-06-19: Fix committed to repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-49346 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-49346?
- Check whether you run struktur AG Libde265 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A heap buffer overflow exists in libde265 prior to version 1.1.0 due to a signed integer overflow in the `de265_image_get_buffer()` function in `image.cc`. When processing a crafted H.265 bitstream with large Sequence Parameter Set (SPS) dimensions and 16-bit bit depth, the calculation for the image plane allocation size (luma_height * luma_bpl) overflows a signed 32-bit integer. This results in a small memory allocation (approx. 1 KB). However, the subsequent `fill_image()` call uses `size_t` arithmetic to calculate the true size, leading to a massive (~4 GB) out-of-bounds write into the undersized heap buffer. The vulnerability is triggered when a user opens a malicious H.265 file. The issue is patched in version 1.1.0.
Affected products
- strukturag libde265 < 1.1.0
Timeline
- 2026-05-26: advisory: Original GitHub Security Advisory published
- 2026-06-19: disclosed: CVE published to NVD
- 2026-06-19: patched: Fix committed to repository