CVE-2026-119341

Tesseract: File-controlled pointers still reach `delete` in ADAPT_CLASS_STRUCT destructor

Published Oct 30, 2026 CVSS 3.1 · 0 Low EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

Tesseract’s adaptive classification engine could read a legacy adaptive template file and, without neutralizing pointer fields, allow file‑controlled pointers to be passed to the ADAPT_CLASS_STRUCT destructor and the delete operator. The resulting improper memory deallocation leads to memory corruption, which can crash the OCR process and cause a denial of service. The weakness involved is a pointer misuse in a destructor (CWE‑763).

Affected Systems

The vulnerability affects all Tesseract OCR engine releases prior to version 5.5.4. The affected component is the adaptive classification module that processes .a template files when the legacy engine is enabled. Updating to any release starting with 5.5.4 removes the flaw.

Risk and Exploitability

Because the flaw is triggered by a user‑controlled .a file, the attack requires write access to the location where the templated file is stored and the legacy engine must be enabled. The EPSS score is not available, and the vulnerability does not appear in the CISA KEV catalog, so at this time the public exploit probability is uncertain. Nonetheless, the flaw can be exercised locally or within any environment that accepts arbitrary template files, making it a high‑risk issue for systems that expose the template generation path to untrusted input.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Tesseract OCR to version 5.5.4 or later, which removes the problematic destructor path.
  • If an upgrade is not immediately possible, disable the legacy adaptive engine by ensuring classify_use_pre_adapted_templates is set to false so that .a files are not loaded.
  • Remove or sanitize any existing pre‑adapted template files from writeable directories to prevent accidental use by Tesseract.

Generated by OpenCVE AI on October 30, 2026 at 21:38 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Tesseract-ocr
Tesseract-ocr tesseract Ocr
Vendors & Products Tesseract-ocr
Tesseract-ocr tesseract Ocr
Type Values Removed Values Added
Description 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.
Title Tesseract: File-controlled pointers still reach `delete` in ADAPT_CLASS_STRUCT destructor
Weaknesses CWE-763
References
Metrics cvssV3_1

{'score': 0, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N'}

Weaknesses
  • CWE-763

    Release of Invalid Pointer or Reference

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 2, 2026, 3:02 PM
Reserved
Oct 29, 2026, 8:44 PM
Status
Awaiting Analysis
Published
Oct 30, 2026, 9:16 PM
Modified
Nov 2, 2026, 7:14 PM
Severity
Moderate
Public date
Oct 30, 2026, 8:24 PM