Skip to content
VulniPulse
Advisory severityHigh7.5Red Hat Linux

High [CVE-2026-54293] Information Disclosure via Path Traversal in `nltk.data.load `

This high-severity Red Hat Linux advisory covers CVE-2026-54293 affecting Red Hat OpenShift AI 2.25, Red Hat OpenShift AI 3.4, Exploit Intelligence.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-54293 Source published Source updated

VulniPulse record published Record updated

Affected products & platforms
Red Hat LinuxUnclassified
Open source advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

NLTK (Natural Language Toolkit) is a suite of open source Python modules, data sets, and tutorials supporting research and development in Natural Language Processing. Prior to 3.10.0-rc1, nltk.data.load() in NLTK is vulnerable to path traversal via URL-encoded path separators and traversal segments when using the nltk: URL scheme.

The unsafe-path regex check is performed before url2pathname() decodes the %xx sequences (a classic decode-after-check / TOCTOU-style flaw), allowing an attacker to bypass the protection documented in NLTK's SECURITY.md and read arbitrary files from the filesystem.

While literal traversal strings such as../../../etc/passwd are correctly blocked, encoded variants such as %2fetc%2fpasswd, %2e%2e%2f..., and..%2f..%2f slip past the regex and are subsequently decoded into a real filesystem path. This vulnerability is fixed in 3.10.0-rc1.

An attacker can exploit a decode-after-check flaw, where URL-encoded path separators and traversal segments bypass security checks. This vulnerability is rated Important because a remote attacker may be able to read arbitrary local files on a system where an application passes untrusted input to nltk.data.load() using the nltk: URL scheme.

Exploitation requires an application that loads NLTK resources from attacker-influenced identifiers.

Affected versions
  • < 3.10.0-rc1

Official advisory · high-confidence parse· fetched 18 days ago·verify at source

Fixed versions
  • 3.10.0
  • rhoai/odh-llama-stack-core-rhel9:1783701598
  • rhoai/odh-ta-lmes-job-rhel9:1787330903
  • rhoai/odh-llama-stack-core-rhel9:1786635926
  • rhoai/odh-pipeline-runtime-pytorch-llmcompressor-cuda-py312-rhel9:1787073459
  • rhoai/odh-trustyai-nemo-guardrails-server-rhel9:1787330585
  • RHSA-2026:42644
  • RHSA-2026:65126
  • RHSA-2026:60520

Official advisory · high-confidence parse· fetched 18 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Update the nltk package to version 3.10.0 or later when a stable release is available. Upstream has fixed this issue in 3.10.0-rc1. Until updated builds are available, do not pass attacker-controlled resource identifiers to nltk.data.load() when using the nltk: URL scheme. Restrict NLTK data loading to trusted, application-controlled paths.

Official advisory · high-confidence parse· fetched 18 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.