CVE-2026-62384
CVE-2026-62384: 1 tracked advisory record across Red Hat. Compare vendor sources and published fix guidance.
Compare the source-linked records below. Ratings and product/version details belong to each advisory; they are not a single CVE-wide score or proof that every listed product is affected. How VulniPulse collects and checks evidence.
Vendor advisory comparison
Red Hat
1 advisory- Advisory severityHigh7.5
High [CVE-2026-62384] Information Disclosure via Symlink Sandbox Bypass
CVE-2026-62384Source published Source updated
NLTK versions before 3.10.2 contain a symlink-based sandbox bypass in FramenetCorpusReader that allows attackers to read arbitrary XML files outside the corpus root. Attackers can place symlinks with names containing no path separators inside the corpus subdirectory, which pass the path validation guard and are resolved to files outside the intended corpus root when accessed via frame_by_name(), _lu_file(), or doc() methods. A flaw was found in NLTK. An attacker can exploit this by placing specially crafted symbolic links within a corpus subdirectory. These symlinks bypass path validation, allowing the attacker to read arbitrary XML files located outside the intended corpus root, leading to information disclosure. A path traversal vulnerability exists in NLTK's FramenetCorpusReader…
- Affected products in this advisory
- Red Hat OpenShift AI 3.3
- Red Hat OpenShift AI 3.5
- Exploit Intelligence
- Lightspeed Core
3 more entries in the full advisory.
- Source-reported affected versions
- < 3.10.2
- Source-reported fixed versions
- rhoai/odh-llama-stack-core-rhel9:1789121286
- rhoai/odh-ta-lmes-job-rhel9:1788935863
- RHSA-2026:73987
- RHSA-2026:69539
- Mitigation guidance
- Restrict write permissions on NLTK corpus subdirectories to prevent unauthorized symlink creation, or sanitize input paths to prevent FramenetCorpusReader from loading untrusted corpus files containing unresolved symbolic links.
Android app · Google Play
Monitor future Red Hat 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.