Bug 2531780

Summary:	CVE-2026-88054 tesseract: Tesseract: Denial of Service via crafted model with empty stack dereference [fedora-all]
Product:	[Fedora] Fedora	Reporter:	Vladimir Vasilev <vvasilev>
Component:	tesseract	Assignee:	Sandro Mani <manisandro>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	epel-packagers-sig, karlikt, manisandro
Target Milestone:	---	Keywords:	Security, SecurityTracking
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	{"flaws": ["e9ddd3bd-629b-4c06-b772-2a59d8f37e1e"]}
Fixed In Version:	tesseract-5.5.3-2.fc45	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2026-09-26 00:16:37 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2531576

Description Vladimir Vasilev 2026-09-11 07:41:18 UTC

Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

Tesseract is an open source OCR engine. In version 5.5.3 and earlier, Plumbing::DeSerialize in src/lstm/plumbing.cpp rejects excessively large network stacks but accepts a zero-length stack for NT_SERIES, NT_PARALLEL, or NT_REVERSED layers in a crafted .traineddata model. During LSTMRecognizer initialization in src/lstm/lstmrecognizer.cpp, CacheXScaleFactor(XScaleFactor()) reaches Series::CacheXScaleFactor in src/lstm/series.cpp, which dereferences stack_[0] on the empty vector and invokes a virtual method through an invalid Network pointer. This causes a deterministic crash and denial of service at model load. No fixed release is available as of this review.

Comment 1 Fedora Update System 2026-09-21 09:16:00 UTC

FEDORA-2026-e3bf7f4ecb (tesseract-5.5.3-2.fc45) has been submitted as an update to Fedora 45.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-e3bf7f4ecb

Comment 2 Fedora Update System 2026-09-21 09:16:22 UTC

FEDORA-2026-4585aba520 (tesseract-5.5.3-2.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-4585aba520

Comment 3 Fedora Update System 2026-09-22 01:35:05 UTC

FEDORA-2026-e3bf7f4ecb has been pushed to the Fedora 45 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-e3bf7f4ecb`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-e3bf7f4ecb

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2026-09-22 01:56:14 UTC

FEDORA-2026-fc27f09459 has been pushed to the Fedora 44 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-fc27f09459`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-fc27f09459

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2026-09-22 02:20:50 UTC

FEDORA-2026-4585aba520 has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-4585aba520`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-4585aba520

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2026-09-26 00:16:37 UTC

FEDORA-2026-e3bf7f4ecb (tesseract-5.5.3-2.fc45) has been pushed to the Fedora 45 stable repository.
If problem still persists, please make note of it in this bug report.