Quick answers
- Is CVE-2026-88054 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-88054 being exploited in the wild.
- How severe is CVE-2026-88054?
- Medium severity, with a CVSS score of 5.5, published 10 September 2026.
- Which products and versions are affected?
- Tesseract OCR Tesseract 5.5.3 and earlier.
- Is there a fix for CVE-2026-88054?
- A patch was published on 2026-08-25: Commit 552771236b0d80cbdb0c7dd856120fa21a4672e5 on 2026-08-25, but no fixed release available as of advisory publication Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-88054 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-88054?
- Check whether you run Tesseract OCR Tesseract 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 a null-pointer dereference in the LSTM (neural network) model deserialization logic. Specifically, Plumbing::DeSerialize in plumbing.cpp validates that network stack sizes are not excessively large (rejecting sizes > 10,000) but fails to reject zero-length stacks for NT_SERIES, NT_PARALLEL, or NT_REVERSED layer types. When LSTMRecognizer initialization calls CacheXScaleFactor(XScaleFactor()) at load time, Series::CacheXScaleFactor unconditionally dereferences stack_[0] on the empty vector, resulting in a virtual method call through a wild pointer. This causes a deterministic crash with no memory corruption—purely a denial of service. The attack requires a locally-supplied or attacker-controlled .traineddata model file; no patch was available as of the advisory publication date.
Affected products
- Tesseract OCR Tesseract 5.5.3 and earlier
Timeline
- 2026-09-10: disclosed
- 2026-08-25: patched: Commit 552771236b0d80cbdb0c7dd856120fa21a4672e5 on 2026-08-25, but no fixed release available as of advisory publication