Tesseract up to 5.5.3 TESSDATA_INTTEMP genericvector.h GenericVector::read reserved/size_used_ out-of-bounds write

Summaryinfo

A vulnerability was found in Tesseract up to 5.5.3. It has been rated as critical. Affected by this vulnerability is the function GenericVector::read of the file src/ccutil/genericvector.h of the component TESSDATA_INTTEMP. Performing a manipulation of the argument reserved/size_used_ results in out-of-bounds write. This vulnerability is identified as CVE-2026-88051. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in Tesseract up to 5.5.3. It has been classified as critical. This affects the function GenericVector::read of the file src/ccutil/genericvector.h of the component TESSDATA_INTTEMP. The manipulation of the argument reserved/size_used_ with an unknown input leads to a out-of-bounds write vulnerability. CWE is classifying the issue as CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Tesseract is an open source OCR engine. In version 5.5.3 and earlier, the callback form of GenericVector::read in src/ccutil/genericvector.h reads the independent int32 fields reserved and size_used_ from a .traineddata model without a cap or an invariant check. reserve(reserved) allocates the backing array, but the callback loop writes size_used_ elements. A crafted TESSDATA_INTTEMP component with version_id 4 or later can therefore set reserved to a small value and size_used_ to a large value when fontinfo_table_.read(fp, read_info) is called from src/classify/intproto.cpp, causing a heap out-of-bounds write of FontInfo structures, heap corruption, a crash, or potentially controlled corruption. No fixed release is available as of this review.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-88051 since 09/09/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/10/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• Tesseract

Version

• 5.5.0
• 5.5.1
• 5.5.2
• 5.5.3

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion