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


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 30 Oct 2026
- **Updated:** 2 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-119341, ECHO-de64-4d5c-048e, GHSA-357f-833m-3f83, UBUNTU-CVE-2026-119341

## What is CVE-2026-119341?

CVE-2026-119341 is a vulnerability in tesseract-ocr tesseract, published on 30 Oct 2026. 

### Official 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.

Weakness: CWE-763 (Release of Invalid Pointer or Reference)

## Which versions are affected by CVE-2026-119341?


## How do I fix CVE-2026-119341?

Upgrade to a fixed version.

## Is CVE-2026-119341 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119341 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119341 and fix it if it is affected.

What it is: CVE-2026-119341 is a vulnerability in tesseract-ocr tesseract, published on 30 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119341 exists.

Affected product: tesseract-ocr tesseract. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-119341/ (Markdown: https://insights.sbomify.com/CVE-2026-119341/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119341
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119341
- OSV: https://osv.dev/vulnerability/CVE-2026-119341

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119341/
Summaries are generated and may contain mistakes; the official description above is the record.