CVE-2026-88054 tesseract-ocr CVE debrief

Who should care

Defenders responsible for Tesseract OCR engine deployments should assess exposure and prioritize verification of engine versions and model loading processes. This includes reviewing and updating model loading and deserialization processes, monitoring for and responding to potential denial of service attacks, and verifying Tesseract OCR engine versions. Additionally, defenders should review compensating controls for exposed systems while remediation is and

Why it matters

The Tesseract OCR engine vulnerability allows for denial of service at model load, which can disrupt OCR engine functionality. Defenders responsible for Tesseract OCR engine deployments should assess exposure and prioritize verification of engine versions and model loading processes.

• Denial of service at model load
• Potential disruption to OCR engine functionality
• Need for verification of Tesseract OCR engine versions
• Possible impact on model loading and deserialization processes

Technical summary

The Tesseract OCR engine is vulnerable to a denial of service attack due to a flaw in the Plumbing::DeSerialize function in src/lstm/plumbing.cpp. The function accepts a zero-length stack for certain layers in a crafted .traineddata model, which can cause a deterministic crash and denial of service at model load. This vulnerability affects Tesseract OCR engine versions 5.5.3 and earlier. The vulnerability allows for denial of service at model load, which can disrupt OCR engine functionality. Defenders should prioritize verifying Tesseract OCR engine versions and updating to a fixed release if available.

Defensive priority

Defenders should prioritize verifying Tesseract OCR engine versions and updating to a fixed release if available, as the vulnerability allows for denial of service at model load.

Recommended defensive actions

• Verify Tesseract OCR engine versions and update to a fixed release if available
• Review and update model loading and deserialization processes
• Monitor for and respond to potential denial of service attacks
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD vulnerability detail indicate that Tesseract OCR engine versions 5.5.3 and earlier are vulnerable to a denial of service attack. The vulnerability is caused by the Plumbing::DeSerialize function in src/lstm/plumbing.cpp accepting a zero-length stack for certain layers in a crafted .traineddata model.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.