CVE-2026-81723 nltk CVE debrief

Who should care

Users of NLTK versions before 3.10.3, particularly those using affected readers like BNCCorpusReader, should be aware of this vulnerability and take defensive actions. This includes reviewing and verifying affected product deployments in managed environments, and implementing compensating controls for CPU consumption. Security teams and vulnerability management teams should prioritize patching or upgrading to version 3.10.3 or later.

Technical summary

NLTK versions before 3.10.3 contain a quadratic CPU exhaustion vulnerability in XMLCorpusView._read_xml_fragment() that rescans accumulated XML fragments on every 1 KiB block read. Attackers can provide malformed XML corpus files to cause severe CPU consumption and denial of service through affected readers like BNCCorpusReader. This issue can lead to significant performance degradation and potential system instability if not addressed.

Defensive priority

Medium-priority defensive actions are recommended due to the CVSS score of 6.3 and potential for denial of service through affected readers.

Recommended defensive actions

• Inventory and verify NLTK version
• Apply patch or upgrade to version 3.10.3 or later
• Monitor for suspicious XML corpus file reads
• Implement compensating controls for CPU consumption
• Review and verify affected product deployments in managed environments
• Track exceptions and retest remediated assets
• Check relevant monitoring, detection, and logs for exposed assets

Evidence notes

Evidence from official sources indicates a quadratic CPU exhaustion vulnerability in NLTK versions before 3.10.3. Limited information is available on affected scope and vendor remediation. Further verification is needed to determine the full impact and to confirm if there are any additional affected readers beyond BNCCorpusReader. Users should review the official CVE record and NVD detail page for more information.

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.