Buffer Overflow Affecting tesseract-devel package, versions *


Severity

Recommended
0.0
high
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.12% (2nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL8-TESSERACTDEVEL-19740363
  • published13 Sept 2026
  • disclosed10 Sept 2026

Introduced: 10 Sep 2026

CVE-2026-88047  (opens in a new tab)
CWE-120  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:8 tesseract-devel.

NVD Description

Note: Versions mentioned in the description apply only to the upstream tesseract-devel package and not the tesseract-devel package as distributed by RHEL. See How to fix? for RHEL:8 relevant fixed versions and status.

Tesseract is an open source OCR engine. In version 5.5.3 and earlier, Classify::ReadNormProtos in src/classify/normmatch.cpp parses the NORMPROTO component of a .traineddata file and uses std::istream::operator>>(char*) to extract a whitespace-delimited token into a fixed 61-byte stack buffer without setting a stream width. The 100-byte line buffer can carry a token of up to 99 characters, so a token longer than 60 characters writes up to 39 attacker-controlled bytes past the buffer during TessBaseAPI::Init of the legacy engine, causing stack corruption, denial of service, and potentially control-flow hijacking on affected standard-library implementations. Builds using Apple's libc++ C++20 bounded array overload are incidentally protected, while typical libstdc++ builds remain affected. No fixed release is available as of this review.

CVSS Base Scores

version 3.1