Quick answers
- Is CVE-2026-88387 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-88387 being exploited in the wild.
- How severe is CVE-2026-88387?
- Informational severity, published 24 September 2026.
- Which products and versions are affected?
- Libraw 0.22.0.
- Is there a fix for CVE-2026-88387?
- A patch was published on 2026-08-07: Fix commit b41cbbd adds type validation to reject FLOAT/DOUBLE TIFF tag types for NewSubfileType Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-88387 attacked?
- It is attacked over the network or with local access, in a software library.
- Am I affected by CVE-2026-88387?
- Check whether you run Libraw 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
The vulnerability is an unsigned-to-signed integer conversion (CWE-681) in LibRaw::parse_tiff_ifd() at src/metadata/tiff.cpp:572. When processing TIFF tag 0x00fe (NewSubfileType), the parser retrieves an unsigned 32-bit value via getreal(type), converts it to double, and then casts it to a signed int without range validation. File-controlled values exceeding INT_MAX trigger undefined behavior; builds with float-cast-overflow sanitization abort with SIGILL. Attack vector is local/network (file opening); no authentication required.
Affected products
- LibRaw LibRaw 0.22.0
Timeline
- 2026-09-24: disclosed
- 2026-08-07: patched: Fix commit b41cbbd adds type validation to reject FLOAT/DOUBLE TIFF tag types for NewSubfileType