How severe is CVE-2026-0846?

CVE-2026-0846 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2026-0846 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (34th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-0846?

CVE-2026-0846 affects Nltk. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-0846?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2026-0846 have an EU (EUVD) identifier?

Yes. CVE-2026-0846 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-10350.

When was CVE-2026-0846 published?

CVE-2026-0846 was published on 2026-03-09 and last updated on 2026-06-30.

CVE-2026-0846

CVE-2026-0846 is a high-severity vulnerability in Nltk with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-36.

Key facts

Severity: High (CVSS 3.x base score 7.5)
EPSS exploit prediction: 0% (34th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-10350
Weakness: CWE-36
Affected product: Nltk
Published: 2026-03-09
Last modified: 2026-06-30

Description

A vulnerability in the `filestring()` function of the `nltk.util` module in nltk version 3.9.2 allows arbitrary file read due to improper validation of input paths. The function directly opens files specified by user input without sanitization, enabling attackers to access sensitive system files by providing absolute paths or traversal paths. This vulnerability can be exploited locally or remotely, particularly in scenarios where the function is used in web APIs or other interfaces that accept user-supplied input.

Frequently asked questions

What is CVE-2026-0846?: A vulnerability in the `filestring()` function of the `nltk.util` module in nltk version 3.9.2 allows arbitrary file read due to improper validation of input paths. The function directly opens files specified by user input without sanitization, enabling attackers to access sensitive system files by providing absolute paths or traversal paths. This vulnerability can be exploited locally or remotely, particularly in scenarios where the function is used in web APIs or other interfaces that accept user-supplied input.
How severe is CVE-2026-0846?: CVE-2026-0846 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2026-0846 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (34th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-0846?: CVE-2026-0846 affects Nltk. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-0846?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-0846 have an EU (EUVD) identifier?: Yes. CVE-2026-0846 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-10350.
When was CVE-2026-0846 published?: CVE-2026-0846 was published on 2026-03-09 and last updated on 2026-06-30.

References

Affected products (1)

cpe:2.3:a:nltk:nltk:3.9.2:*:*:*:*:*:*:*

More vulnerabilities in Nltk

CVE-2026-0848 — Critical (CVSS 10.0): NLTK versions <=3.9.2 are vulnerable to arbitrary code execution due to improper input validation in the…
CVE-2025-14009 — High (CVSS 8.8): A critical vulnerability exists in the NLTK downloader component of nltk/nltk, affecting all versions. The _unzip_iter…
CVE-2026-33236 — High (CVSS 8.1): NLTK (Natural Language Toolkit) is a suite of open source Python modules, data sets, and tutorials supporting research…
CVE-2026-12243 — High (CVSS 7.5): NLTK version 3.9.4 is vulnerable to a path traversal attack due to an incomplete fix for GitHub Issue #3504. The…
CVE-2026-54293 — High (CVSS 7.5): NLTK (Natural Language Toolkit) is a suite of open source Python modules, data sets, and tutorials supporting research…
CVE-2026-33231 — High (CVSS 7.5): NLTK (Natural Language Toolkit) is a suite of open source Python modules, data sets, and tutorials supporting research…

All CVEs affecting Nltk →

Other CWE-36 vulnerabilities

CVE-2023-3765 — Critical (CVSS 10.0): Absolute Path Traversal in GitHub repository mlflow/mlflow prior to 2.5.0.
CVE-2025-34392 — Critical (CVSS 9.8): Barracuda Service Center, as implemented in the RMM solution, in versions prior to 2025.1.1, does not verify the URL…
CVE-2025-0851 — Critical (CVSS 9.8): A path traversal issue in ZipUtils.unzip and TarUtils.untar in Deep Java Library (DJL) on all platforms allows a bad…
CVE-2024-13161 — Critical (CVSS 9.8): Absolute path traversal in Ivanti EPM before the 2024 January-2025 Security Update and 2022 SU6 January-2025 Security…
CVE-2024-13160 — Critical (CVSS 9.8): Absolute path traversal in Ivanti EPM before the 2024 January-2025 Security Update and 2022 SU6 January-2025 Security…
CVE-2024-13159 — Critical (CVSS 9.8): Absolute path traversal in Ivanti EPM before the 2024 January-2025 Security Update and 2022 SU6 January-2025 Security…

Browse all CWE-36 vulnerabilities →