Quick answers
- Is CVE-2026-12600 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-12600 being exploited in the wild.
- How severe is CVE-2026-12600?
- Informational severity, published 25 August 2026.
- Which products and versions are affected?
- Innodata Labs Poppler <unknown>.
- Is there a fix for CVE-2026-12600?
- 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-12600 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-12600?
- Check whether anything you run is named in the advisory. 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 denial-of-service vulnerability exists in the JPXStream::readCodestream() function within the JPX (JPEG2000) decoder of the Innodata Labs Poppler fork. The vulnerable code fails to validate size values (such as img.nComps) extracted from the SIZ segment of JPXDecode images before using them in memory allocation calculations for tiles and components. This allows an attacker to craft a malicious PDF with unvalidated image parameters that trigger uncontrolled memory allocation. When an application processes such a PDF, the decoder will exhaust available system memory, causing the PDF processing process to terminate via out-of-memory (OOM) conditions. No patch information is currently available.
Affected products
- Innodata Labs Poppler <unknown>
Timeline
- 2026-08-25: disclosed