# CVE-2026-119339: Tesseract is an open source OCR engine.


- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 30 Oct 2026
- **Updated:** 30 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-119339, ECHO-acdf-44a6-a427, GHSA-h9g4-frjx-6cj3, UBUNTU-CVE-2026-119339

## What is CVE-2026-119339?

CVE-2026-119339 is a medium-severity vulnerability in tesseract-ocr tesseract, published on 30 Oct 2026. 

### Official description

Tesseract is an open source OCR engine. Prior to 5.5.4, WeightMatrix::DeSerialize trusts a mode byte from a traineddata LSTM network and calls WeightMatrix::DeSerializeOld when kDoubleFlag is clear. In default FAST_FLOAT builds, DeSerializeOld invokes ASSERT_HOST instead of returning an error, so loading a crafted model through TessBaseAPI::Init terminates the process and causes denial of service. This issue is fixed in version 5.5.4.

Weakness: CWE-617 (Reachable Assertion), CWE-20 (Improper Input Validation)

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


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

Upgrade to a fixed version.

## Is CVE-2026-119339 being exploited?

There is no known exploitation of CVE-2026-119339 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-119339 is a medium-severity vulnerability in tesseract-ocr tesseract, published on 30 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119339 in the wild and no public exploit code.

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-119339/ (Markdown: https://insights.sbomify.com/CVE-2026-119339/index.md)
```

## Sources

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

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