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

Q: What conditions are required for exploitation?

The legacy engine must be selected, classify_use_pre_adapted_templates must be enabled, and an attacker must be able to write the output-basename .a pre-adapted-template file. The vulnerable code then reads attacker-controlled pointer values from that file.

Q: Are default deployments affected?

The issue is not described as affecting all default deployments. Exploitation depends on use of the legacy engine and enabling pre-adapted templates, in addition to attacker write access to the relevant .a file.

Q: What is the impact if exploitation succeeds?

File-controlled pointers can reach the ADAPT_CLASS_STRUCT destructor and operator delete, causing memory corruption and denial of service. The provided severity vector indicates no confidentiality or integrity impact.

Q: What can be done if upgrading is not immediately possible?

Prevent untrusted parties from writing the output-basename .a file, and avoid the affected configuration by not selecting the legacy engine or by disabling classify_use_pre_adapted_templates where operationally feasible.

Q: What version contains the fix?

The issue is fixed in Tesseract version 5.5.4. Versions prior to 5.5.4 are described as affected under the required configuration and file-write conditions.

Published Oct 30, 2026

Updated

Tesseract is an open source OCR engine. Prior to 5.5.4, ReadAdaptedClass in src/classify/adaptive.cpp raw-reads an ADAPTCLASSSTRUCT from a pre-adapted-template .a file without neutralizing TempProtos and Config pointer fields before any destructor path. When the legacy engine is selected, classifyusepreadaptedtemplates is enabled, and an attacker can write the output-basename .a file, the success or rejection path can pass file-controlled pointers to ~ADAPTCLASSSTRUCT and operator delete, causing memory corruption and denial of service. This issue is fixed in version 5.5.4.

Affected Software

12 affected components

debian/tesseract<=5.3.0-2, <=5.5.0-1, <=5.5.0-1.1

debian/tesseract*

ubuntu/tesseract*

Event History

Oct 30, 2026

CVE Published

via MITRE·08:24 PM

Data Sourced

via MITRE·08:24 PM

DescriptionSeverityWeakness

Data Sourced

via NVD·09:16 PM

DescriptionSeverityWeakness

Data Sourced

via OSV·09:16 PM

Affected Software

Frequently Asked Questions

What conditions are required for exploitation?

The legacy engine must be selected, classify_use_pre_adapted_templates must be enabled, and an attacker must be able to write the output-basename .a pre-adapted-template file. The vulnerable code then reads attacker-controlled pointer values from that file.

Are default deployments affected?

The issue is not described as affecting all default deployments. Exploitation depends on use of the legacy engine and enabling pre-adapted templates, in addition to attacker write access to the relevant .a file.

What is the impact if exploitation succeeds?

File-controlled pointers can reach the ADAPT_CLASS_STRUCT destructor and operator delete, causing memory corruption and denial of service. The provided severity vector indicates no confidentiality or integrity impact.

What can be done if upgrading is not immediately possible?

Prevent untrusted parties from writing the output-basename .a file, and avoid the affected configuration by not selecting the legacy engine or by disabling classify_use_pre_adapted_templates where operationally feasible.

What version contains the fix?

The issue is fixed in Tesseract version 5.5.4. Versions prior to 5.5.4 are described as affected under the required configuration and file-write conditions.

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

Affected Software

Event History

Frequently Asked Questions

What conditions are required for exploitation?

Are default deployments affected?

What is the impact if exploitation succeeds?

What can be done if upgrading is not immediately possible?

What version contains the fix?

Company

Resources

Contact

Frequently Asked Questions

What conditions are required for exploitation?

Are default deployments affected?

What is the impact if exploitation succeeds?

What can be done if upgrading is not immediately possible?

What version contains the fix?