Quick answers
- Is CVE-2026-45382 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45382 being exploited in the wild.
- How severe is CVE-2026-45382?
- Informational severity, with a CVSS score of 6.9, published 21 July 2026.
- Which products and versions are affected?
- struktur AG Libde265 < 1.0.19.
- Is there a fix for CVE-2026-45382?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-45382 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-45382?
- 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 (OOB) read vulnerability exists in libde265 prior to version 1.0.19 within the `decoder_context::decode_slice_unit_tiles` function in `decctx.cc`. The root cause is a failure to validate the `ctbAddrRS` index, calculated from Picture Parameter Set (PPS) supplied `colBd[]` and `rowBd[]` arrays, against the size of the `CtbAddrRStoTS` vector. An attacker can provide a malformed PPS with geometry inconsistent with the Sequence Parameter Set (SPS) to trigger a 4-byte heap-buffer-overflow read. This vulnerability specifically affects the parallel-tile decoding path when worker threads are enabled. The issue is fixed in version 1.0.19.
Affected products
- strukturag libde265 < 1.0.19
Timeline
- 2026-05-19: advisory: GitHub Security Advisory published
- 2026-07-21: disclosed: NVD publication date