Live › vulnerability › CVE-2026-119341
Tesseract, an open source OCR engine, reads a pre-adapted template (.a) file without validating pointer fields, so a crafted file can trigger invalid memory frees during classification. An attacker who can write that file can cause memory corruption and denial of service.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-30 21:25 UTC. All times on this page are UTC.
Only setups that run Tesseract before 5.5.4 with the legacy OCR engine selected and classify_use_pre_adapted_templates enabled, and where an attacker can write the output-basename .a file. Systems using the default LSTM engine or without that setting are not described as exposed by the sources.
No product ranges from the sources yet.
tesseract --version; versions before 5.5.4 are in scope.classify_use_pre_adapted_templates is enabled in your configuration..a file location.5.5.4 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Tesseract is an open source OCR engine. Prior to 5.5.4, ReadAdaptedClass in src/classify/adaptive.cpp raw-reads an ADAPT_CLASS_STRUCT from a pre-adapted-template .a file without neutralizing TempProtos and Config pointer fields before any destructor path. When the legacy engine is selected, classify_use_pre_adapted_templates is enabled, and an attacker can write the output-basename .a file, the success or rejection path can pass file-controlled pointers to ~ADAPT_CLASS_STRUCT and operator delete, causing memory corruption and denial of service. This issue is fixed in version 5.5.4.
This page as .md · .json · in your agent: get_signal("CVE-2026-119341")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.