Quick answers
- Is CVE-2026-49295 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-49295 being exploited in the wild.
- How severe is CVE-2026-49295?
- High severity, with a CVSS score of 7.1, published 19 June 2026.
- Which products and versions are affected?
- struktur AG Libde265 < 1.0.20.
- Is there a fix for CVE-2026-49295?
- A patch was published on 2026-06-19: Fix committed in version 1.0.20 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-49295 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-49295?
- 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
An out-of-bounds write vulnerability exists in libde265 within the `decoder_context::process_reference_picture_set()` function in `decctx.cc`. The issue stems from a missing aggregate bound check when constructing predicted short-term reference picture sets (RPS). While individual list sizes are validated, the combined count of entries after predicted RPS construction can exceed the 16-entry limit of the `PocStFoll` array, leading to a write at index 16. An attacker can exploit this by providing a crafted H.265 bitstream with `inter_ref_pic_set_prediction_flag=1` that results in 17 entries. This is a remote attack vector requiring user interaction (opening a file) and can result in memory corruption, application crashes, or potential arbitrary code execution. The vulnerability is patched in version 1.0.20.
Affected products
- strukturag libde265 < 1.0.20
Timeline
- 2026-05-26: advisory: GitHub Security Advisory published
- 2026-06-19: disclosed: NVD publication date
- 2026-06-19: patched: Fix committed in version 1.0.20