Bug 2531546 (CVE-2026-88048) - CVE-2026-88048 tesseract: Tesseract: Heap out-of-bounds write/read leading to information disclosure via crafted data
Summary: CVE-2026-88048 tesseract: Tesseract: Heap out-of-bounds write/read leading to...
Keywords:
Status: NEW
Alias: CVE-2026-88048
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2531774
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-10 16:32 UTC by OSIDB Bzimport
Modified: 2026-11-11 12:06 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:95085 0 None None None 2026-11-04 11:44:25 UTC
Red Hat Product Errata RHSA-2026:95086 0 None None None 2026-11-04 13:04:17 UTC
Red Hat Product Errata RHSA-2026:95725 0 None None None 2026-11-05 23:24:39 UTC
Red Hat Product Errata RHSA-2026:96238 0 None None None 2026-11-09 11:53:00 UTC
Red Hat Product Errata RHSA-2026:96239 0 None None None 2026-11-09 11:41:29 UTC
Red Hat Product Errata RHSA-2026:98514 0 None None None 2026-11-11 12:06:56 UTC
Red Hat Product Errata RHSA-2026:98624 0 None None None 2026-11-11 11:41:20 UTC

Description OSIDB Bzimport 2026-09-10 16:32:25 UTC 
Tesseract is an open source OCR engine. In version 5.5.3 and earlier, FullyConnected::DeSerialize in src/lstm/fullyconnected.cpp does not validate the deserialized layer scalars ni_ and no_ against the weight-matrix dimensions. During FullyConnected::Forward, MatrixDotVector in src/lstm/weightmatrix.cpp writes w.dim1() results into temp_line, which is sized from no_, and reads w.dim2() minus one inputs from curr_input, which is sized from ni_. A crafted .traineddata NT_SOFTMAX layer can therefore use inconsistent dimensions to cause a heap out-of-bounds write and read on the default LSTM engine, resulting in heap corruption, a crash, information disclosure, or potentially controlled corruption. No fixed release is available as of this review.
Comment 1 Jon Orris 2026-11-04 11:44:24 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:95085 https://access.redhat.com/errata/RHSA-2026:95085
Comment 2 Jon Orris 2026-11-04 13:04:16 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:95086 https://access.redhat.com/errata/RHSA-2026:95086
Comment 3 Jon Orris 2026-11-05 23:24:38 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:95725 https://access.redhat.com/errata/RHSA-2026:95725
Comment 4 errata-xmlrpc 2026-11-09 11:41:27 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support
  Red Hat Enterprise Linux 8.6 Extended Update Support Long-Life Add-On

Via RHSA-2026:96239 https://access.redhat.com/errata/RHSA-2026:96239
Comment 5 errata-xmlrpc 2026-11-09 11:52:59 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions
  Red Hat Enterprise Linux 8.8 Telecommunications Update Service

Via RHSA-2026:96238 https://access.redhat.com/errata/RHSA-2026:96238
Comment 6 errata-xmlrpc 2026-11-11 11:41:19 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:98624 https://access.redhat.com/errata/RHSA-2026:98624
Comment 7 errata-xmlrpc 2026-11-11 12:06:55 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:98514 https://access.redhat.com/errata/RHSA-2026:98514
Note You need to log in before you can comment on or make changes to this bug.