Heap corruption via mismatched LSTM dimensions
Published Sep 10, 2026 · Updated Sep 10, 2026
Heap out-of-bounds write in Tesseract 5.5.3 and earlier allows context-dependent attackers to crash OCR via crafted traineddata. LSTM::Forward sizes source_ from the deserialized na_ value, then WriteTimeStepPart copies ns_ elements from the CI gate matrix without checking destination bounds. The crafted NT_LSTM layer must be loaded for recognition; the first LSTM step can corrupt heap memory or terminate the process.
Summary
What happened
Heap out-of-bounds write in Tesseract 5.5.3 and earlier allows context-dependent attackers to crash OCR via crafted traineddata. LSTM::Forward sizes source_ from the deserialized na_ value, then WriteTimeStepPart copies ns_ elements from the CI gate matrix without checking destination bounds. The crafted NT_LSTM layer must be loaded for recognition; the first LSTM step can corrupt heap memory or terminate the process.
The record
- CVE
- CVE-2026-88049
- Published
- Sep 10, 2026
- Updated
- Sep 10, 2026
- Vendor
- Tesseract OCR
- Product
- Tesseract
- Classifications
- T1204.002
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 10, 2026CVE publishedPublication date reported by the CVE source.
- Sep 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=<= 5.5.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo