Evidence used
- No CISA KEV confirmation is currently recorded.
- A structured source references public exploit or proof-of-concept material.
- EPSS is 0.15% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-88049High confidence
Tesseract: Heap out-of-bounds write in LSTM::Forward via na_/gate-matrix dimension mismatch
tesseract-ocr · tesseract
Official source article: GitHub GHSA-JGQ8-PPRG-VC68 ↗. Check the applicable product and release in the original source.
8.6HighCVSS 4.0
Patch only the product branches with a verified fix
Fix availability varies by productHigh technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 210 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:High, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict local access and enforce least privilege on affected hosts.
- Increase monitoring for the attack path and post-exploitation behaviour described in the report.
Verification
- Confirm that the asset runs tesseract-ocr tesseract and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 210 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Red Hat Product Security: 206 affected or under-investigation product states without a fixed product state in the same current advisory
- Debian Security Tracker: 4 affected package states with no published fix
Distribution package intelligence
5 package statesRelease-specific package status
Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Package result overrides the generic status
BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 4 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | tesseract | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian bookwormbookworm · source | tesseract | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian forkyforky · source | tesseract | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian sidsid · source | tesseract | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | tesseract | Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2026-88049 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitytesseract: Tesseract: Heap out-of-bounds write allows arbitrary code execution or denial of service
The vendor explicitly identifies these products as affected by this CVE.
- tesseract-devel as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-afr as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-amh as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-ara as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-asm as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-aze as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-aze_cyrl as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-bel as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-ben as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-bod as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-bos as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-bul as a component of Red Hat Enterprise Linux 10
- Summary
- A flaw was found in Tesseract, an open-source Optical Character Recognition (OCR) engine. A remote attacker could exploit a heap out-of-bounds write vulnerability in the `LSTM::Forward` function by providing a specially crafted input. This could lead to heap corruption, application crashes, or potentially controlled memory corruption, which may result in arbitrary code execution or a denial of service.
- Remediation
- To mitigate this issue, avoid processing `.traineddata` files from untrusted or unverified sources with Tesseract. Restricting the application's input to only trusted `.traineddata` files can prevent exploitation of this vulnerability.
High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 210 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
Tesseract is an open source OCR engine. In version 5.5.3 and earlier, prior .traineddata hardening added bounds checks to NetworkIO::CopyTimeStepGeneral and NetworkIO::Randomize in src/lstm/networkio.cpp but left NetworkIO::WriteTimeStepPart and NetworkIO::AddTimeStepPart unchecked. In LSTM::Forward in src/lstm/lstm.cpp, source_ is sized from the independently deserialized na_ field while the WriteTimeStepPart count is ns_, which comes from the CI gate WeightMatrix dim1() value. A crafted NT_LSTM layer can make ns_ much larger than na_, causing a heap out-of-bounds write during the first recognition step on the default LSTM engine and resulting in heap corruption, a crash, or potentially controlled corruption. No fixed release is available as of this review.
What
Tesseract is an open source OCR engine. In version 5.5.3 and earlier, prior .traineddata hardening added bounds checks to NetworkIO::CopyTimeStepGeneral and NetworkIO::Randomize in src/lstm/networkio.cpp but left NetworkIO::WriteTimeStepPart and NetworkIO::AddTimeStepPart unchecked. In LSTM::Forward in src/lstm/lstm.cpp, source_ is sized from the independently deserialized na_ field while the WriteTimeStepPart count is ns_, which comes from the CI gate WeightMatrix dim1() value. A crafted NT_LSTM layer can make ns_ much larger than na_, causing a heap out-of-bounds write during the first recognition step on the default LSTM engine and resulting in heap corruption, a crash, or potentially controlled corruption. No fixed release is available as of this review.
Why
A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.
How
An attacker operating through local access may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.
What
Tesseract is an open source OCR engine. In version 5.5.3 and earlier, prior .traineddata hardening added bounds checks to NetworkIO::CopyTimeStepGeneral and NetworkIO::Randomize in src/lstm/networkio.cpp but left NetworkIO::WriteTimeStepPart and NetworkIO::AddTimeStepPart unchecked. In LSTM::Forward in src/lstm/lstm.cpp, source_ is sized from the independently deserialized na_ field while the WriteTimeStepPart count is ns_, which comes from the CI gate WeightMatrix dim1() value. A crafted NT_LSTM layer can make ns_ much larger than na_, causing a heap out-of-bounds write during the first recognition step on the default LSTM engine and resulting in heap corruption, a crash, or potentially controlled corruption. No fixed release is available as of this review.
Why
A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.
How
An attacker operating through local access may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material Reference recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.CISA Vulnrichment records proof-of-concept exploitation in its SSVC data. BlackTree has not independently executed or validated exploit material.
- Likely attack path
- local access → Out-of-bounds Write → disrupt the affected service
- Attack surface
- Local
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Not a CVSS 4.0 base metric
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-787 ↗
CWE-787: Out-of-bounds Write. The product writes data past the end, or before the beginning, of the intended buffer.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NCommon Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATNoneAttack requirements: No additional deployment or execution condition is required.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.VCHighVulnerable-system confidentiality: A successful attack can cause a major loss.VIHighVulnerable-system integrity: A successful attack can cause a major loss.VAHighVulnerable-system availability: A successful attack can cause a major loss.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.- Post-exploitation / living off the land
- The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix availability varies by product
- Affected
- tesseract-devel as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-afr as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-amh as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-ara as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-asm as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-aze as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-aze_cyrl as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-bel as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-ben as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-bod as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-bos as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-bul as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-cat as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-ceb as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-ces as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-chi_sim as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-chi_tra as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-chr as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-cym as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-dan as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-deu as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-dzo as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-ell as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-enm as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-epo as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-est as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-eus as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-fas as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-fin as a component of Red Hat Enterprise Linux 10
- tesseract-langpack-fra as a component of Red Hat Enterprise Linux 10
- and 176 more
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- Workaround
- To mitigate this issue, avoid processing `.traineddata` files from untrusted or unverified sources with Tesseract. Restricting the application's input to only trusted `.traineddata` files can prevent exploitation of this vulnerability.
Official vendor articles1 stored document
Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.
- Heap out-of-bounds write in LSTM::Forward via na_/gate-matrix dimension mismatch · Advisory · tesseract-ocr/tesseract · GitHub →Original publisher ↗Searchable text snapshot · Captured 26 Sep 2026tesseract-ocr / tesseract Public Notifications You must be signed in to change notification settings Fork 10.8k Star 76.7k Code Issues 437 Pull requests 50 Actions Projects Wiki Security and quality 10 Insights Additional navigation options Code Issues Pull requests Actions Projects Wiki Security and
04
Evidence and provenance
Published 10 Sept 2026 · Last source change 10 Sept 2026, 17:13 UTC · CWE-787 · Out-of-bounds Write
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-09-11
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-75592
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- ENISA EUVD mappingEUVD-2026-75592 was added to the official ENISA EUVD mapping for this CVE.ENISA EUVD ↗
- Before
- not recorded
- After
- {"euvdId":"EUVD-2026-75592"}
- Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-88049 to remediation: access.redhat.com/CVE-2026-88049.Red Hat Product Security ↗
- Before
- remediation: access.redhat.com/CVE-2026-88049
- After
- remediation: access.redhat.com/CVE-2026-88049
- Remediation statusRemediation status changed from Awaiting fix to Mitigation available.Red Hat Product Security ↗
- Before
- Awaiting fix
- After
- Mitigation available
- Vendor guidanceAuthoritative vendor guidance changed: added patch: github.com/b494ac18925f9d9aff9ef5815475de9943ab19bf; added remediation: github.com/b494ac18925f9d9aff9ef5815475de9943ab19bf; 1 further additions.github.com ↗
- Before
- no authoritative guidance recorded
- After
- patch: github.com/b494ac18925f9d9aff9ef5815475de9943ab19bf · remediation: github.com/b494ac18925f9d9aff9ef5815475de9943ab19bf · vendor advisory: github.com/GHSA-jgq8-pprg-vc68
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- <= 5.5.3 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- tesseract: <= 5.5.3 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- Remediation statusRemediation status changed from Awaiting fix to Patch available.github.com ↗
- Before
- Awaiting fix
- After
- Patch available
- Public exploit evidencePublic exploit evidence changed from No public exploit to Public exploit reference.CVE.org ↗
- Before
- No public exploit
- After
- Public exploit reference
- Catalogue recordCVE added to the BlackTree catalogue.CNA ↗
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.