Red Hat Tesseract Update Fixes RHEL 9 Parsing Flaw
Tech GuruQuick Answer
RHSA-2026:72280 fixes a Tesseract buffer-overflow risk in crafted .traineddata model components. The listed RHEL 9.2 E4S fix is 4.1.1-7.el9_2.1. Review where OCR models come from as well as the package version; this notice is specifically about trained-data processing.
Confirm Scope And Apply The Supported Fix
Next step: Inventory OCR workers and model locations, confirm the entitled RHEL 9.2 repository, and install the supported update. Keep model files from approved sources while investigating exposure.
Last verified: 2026-09-28 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | RHEL 9.2 E4S tesseract packages before 4.1.1-7.el9_2.1 |
|---|---|
| Advisory | RHSA-2026:72280 |
| CVE | CVE-2026-73066 |
| Authoritative release date | RHSA-2026:72280: 2026-09-28 03:07:33 UTC |
| Authority revision date | RHSA-2026:72280: 2026-09-28 03:30:01 UTC |
| Affected versions | Entitled RHEL 9.2 Update Services for SAP Solutions systems using tesseract before 4.1.1-7.el9_2.1 to process potentially untrusted trained-data files. |
| Fixed version | tesseract 4.1.1-7.el9_2.1 |
| CVSS base score | 7.1 (CVSS v3.1) |
| CVSS severity | High |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
The flaw involves an undersized allocation while deserializing an LSTM model component, with possible denial of service or code execution. A model file is therefore not harmless merely because it is described as data. The advisory does not show that every ordinary scanned image triggers this vulnerability.
What To Validate Now
- Inventory. Locate RHEL 9.2 E4S tesseract packages before 4.1.1-7.el9_2.1 deployments, versions, enabled features, exposure paths, owners, and dependent services.
- Establish applicability. Compare each deployment with the authority's affected-version statement: Entitled RHEL 9.2 Update Services for SAP Solutions systems using tesseract before 4.1.1-7.el9_2.1 to process potentially untrusted trained-data files. Do not infer applicability from product family or severity alone.
- Remediate. Apply tesseract 4.1.1-7.el9_2.1 through the supported vendor or project channel, following the current advisory and change-control requirements.
- Validate. Verify the Tesseract binary and models used by each worker, then run representative authorized documents and compare recognition output and errors. Test isolated regression fixtures separately. Retain model provenance without copying confidential scanned documents into the change record.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Treat OCR models and trained-data files as executable-risk inputs. Prefer trusted data until patched, test recognition quality after the package change, and do not infer exploitation from the High score.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
