VulnerabilityPublished 30 Oct 2026

CVE-2026-119341: tesseract · Release of Invalid Pointer or Reference

Affects tesseractSource CVE Database V5

Compare

Not known to be exploited · CVSS 0.0 High : upgrade to 5.5.3 soon.

Data as of 30 Oct 2026, 20:51 UTC

CVSS 3.1 base score

0.0High

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (GitHub_M)	CVSS 3.1	0.0

Patch: Available – fixed in 5.5.3, 5.5.4

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade tesseract to 5.5.3; tesseract-ocr/tesseract to 5.5.4.

Affected software

Product	Affected	Fixed in
tesseract-ocrtesseract	Affected <5.5.3	Fixed in 5.5.3
GitHubtesseract-ocr/tesseract`pkg:github/tesseract-ocr/tesseract`Other threats	Affected <5.5.4	Fixed in 5.5.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to Tesseract version 5.5.4 or later, where this vulnerability is fixed. No other mitigation actions are indicated.

Description

CVE-2026-119341 is a vulnerability in the open source OCR engine Tesseract prior to version 5.5.4. It involves improper handling of pointers when reading ADAPT_CLASS_STRUCT data from pre-adapted-template files, which can lead to memory corruption and denial of service. The issue is fixed in version 5.5.4.

Impact

Exploitation of this vulnerability can cause memory corruption and denial of service in affected Tesseract versions. There is no indication of confidentiality or integrity impact. No known exploits are reported in the wild.

Summary

Tesseract versions before 5.5.4 contain a vulnerability in the ReadAdaptedClass function located in src/classify/adaptive.cpp. The function raw-reads an ADAPT_CLASS_STRUCT from a pre-adapted-template .a file without neutralizing the TempProtos and Config pointer fields before any destructor path. When the legacy engine is selected and classify_use_pre_adapted_templates is enabled, an attacker who can write the output-basename .a file may cause the success or rejection path to pass file-controlled pointers to the destructor ~ADAPT_CLASS_STRUCT and operator delete. This leads to memory corruption and potential denial of service. The vulnerability is addressed in Tesseract version 5.5.4.

CWE-763Release of Invalid Pointer or Reference (opens in a new tab)
Base weakness
The product attempts to return a memory resource to the system, but it calls the wrong release function or calls the appropriate release function incorrectly.
Implementation
Only call matching memory management functions. Do not mix and match routines. For example, when you allocate a buffer with malloc(), dispose of the original pointer with free().
Implementation
When programming in C++, consider using smart pointers provided by the boost library to help correctly and consistently manage memory.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Oct 2026, 20:51 UTC

WeaknessesCWE-763

Technical details

References

Community reviews

Related threats