CVE-2026-0848

CRITICALNVD 10.010.0—
EchelonGraph scoreMEDIUM confidence

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-03-05. NVD baseline CVSS 10.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
10.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 10.0Exploit: Elevated riskExposed: 0

A fix is available — apply it.

NLTK versions <=3.9.2 are vulnerable to arbitrary code execution due to improper input validation in the StanfordSegmenter module. The module dynamically loads external Java .jar files without verification or sandboxing. An attacker can supply or replace the JAR file, enabling the execution of arbitrary Java bytecode at import time. This vulnerability can be exploited through methods such as model poisoning, MITM attacks, or dependency poisoning, leading to remote code execution. The issue arises from the direct execution of the JAR file via subprocess with unvalidated classpath input, allowing malicious classes to execute when loaded by the JVM.

CVSS v3
10.0
EG Score
10.0(medium)
EG Risk
76(Attend)
EG Risk 76/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity100% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
53%
KEV
Not listed

Published

March 5, 2026

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated Jul 25, 2026
No patch confirmed yet.
generic

huntr - The world's first bug bounty platform for AI/ML

https://huntr.com/bounties/08b109bb-ac24-403f-9422-1c246ce60202

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3-nltk (3.7-1ubuntu0.1~esm2) @ jammy2026-06-12ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
nltk0.8 ... 3.9b1 (63 versions)3.9.3—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 9× in last 7d / 36× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 139 total refreshes for this CVE.

  1. 2026-07-26 14:54 UTCEPSS rescore
  2. 2026-07-26 14:54 UTCEPSS rescore
  3. 2026-07-25 14:17 UTCEPSS rescore
  4. 2026-07-24 14:17 UTCEPSS rescore
  5. 2026-07-23 14:18 UTCEPSS rescore
  6. 2026-07-23 03:04 UTCEG score recompute
  7. 2026-07-22 14:08 UTCEPSS rescore
  8. 2026-07-21 15:24 UTCEPSS rescore
  9. 2026-07-20 17:08 UTCEPSS rescore
  10. 2026-07-19 14:30 UTCEPSS rescore
  11. 2026-07-19 02:28 UTCEPSS rescore
  12. 2026-07-18 10:04 UTCEPSS rescore
  13. 2026-07-17 16:29 UTCOSV refresh
  14. 2026-07-16 17:02 UTCEPSS rescore
  15. 2026-07-15 16:57 UTCEPSS rescore
  16. 2026-07-15 02:00 UTCEPSS rescore
  17. 2026-07-13 22:30 UTCEPSS rescore
  18. 2026-07-13 06:12 UTCEPSS rescore
  19. 2026-07-12 05:46 UTCEPSS rescore
  20. 2026-07-11 08:27 UTCEPSS rescore
  21. 2026-07-09 19:10 UTCEPSS rescore
  22. 2026-07-08 15:15 UTCEPSS rescore
  23. 2026-07-08 15:15 UTCEPSS rescore
  24. 2026-07-07 13:46 UTCEPSS rescore
  25. 2026-07-06 16:27 UTCEPSS rescore
Show 75 more
  1. 2026-07-06 02:23 UTCEPSS rescore
  2. 2026-07-05 02:30 UTCEPSS rescore
  3. 2026-07-05 02:30 UTCEPSS rescore
  4. 2026-07-04 06:31 UTCEPSS rescore
  5. 2026-07-01 15:06 UTCEPSS rescore
  6. 2026-07-01 15:06 UTCEPSS rescore
  7. 2026-06-30 23:22 UTCEPSS rescore
  8. 2026-06-29 14:06 UTCEPSS rescore
  9. 2026-06-28 14:07 UTCEPSS rescore
  10. 2026-06-28 04:56 UTCEPSS rescore
  11. 2026-06-28 04:56 UTCEPSS rescore
  12. 2026-06-27 03:08 UTCEPSS rescore
  13. 2026-06-25 13:49 UTCEPSS rescore
  14. 2026-06-24 14:05 UTCEPSS rescore
  15. 2026-06-23 21:32 UTCEPSS rescore
  16. 2026-06-22 14:25 UTCEPSS rescore
  17. 2026-06-22 14:25 UTCEPSS rescore
  18. 2026-06-21 14:56 UTCEPSS rescore
  19. 2026-06-21 14:56 UTCEPSS rescore
  20. 2026-06-21 01:59 UTCEPSS rescore
  21. 2026-06-21 01:59 UTCEPSS rescore
  22. 2026-06-19 19:25 UTCEPSS rescore
  23. 2026-06-18 17:52 UTCEPSS rescore
  24. 2026-06-17 17:53 UTCEPSS rescore
  25. 2026-06-16 17:52 UTCEPSS rescore
  26. 2026-06-15 17:48 UTCEPSS rescore
  27. 2026-06-14 23:18 UTCEPSS rescore
  28. 2026-06-13 23:00 UTCEPSS rescore
  29. 2026-06-13 23:00 UTCEPSS rescore
  30. 2026-06-12 23:12 UTCEPSS rescore
  31. 2026-06-12 04:41 UTCVendor advisory
  32. 2026-06-12 04:41 UTCGHSA enrichment
  33. 2026-06-12 00:39 UTCVendor advisory
  34. 2026-06-12 00:39 UTCGHSA enrichment
  35. 2026-06-11 14:00 UTCEPSS rescore
  36. 2026-06-10 23:16 UTCVendor advisory
  37. 2026-06-10 23:16 UTCGHSA enrichment
  38. 2026-06-10 22:18 UTCEPSS rescore
  39. 2026-06-10 18:50 UTCVendor advisory
  40. 2026-06-10 18:50 UTCGHSA enrichment
  41. 2026-06-10 13:22 UTCEPSS rescore
  42. 2026-06-10 11:01 UTCVendor advisory
  43. 2026-06-10 11:01 UTCGHSA enrichment
  44. 2026-06-10 06:25 UTCVendor advisory
  45. 2026-06-10 06:25 UTCGHSA enrichment
  46. 2026-06-10 01:56 UTCVendor advisory
  47. 2026-06-10 01:56 UTCGHSA enrichment
  48. 2026-06-09 17:42 UTCVendor advisory
  49. 2026-06-09 17:42 UTCGHSA enrichment
  50. 2026-06-08 14:17 UTCEPSS rescore
  51. 2026-06-08 14:17 UTCEPSS rescore
  52. 2026-06-08 09:27 UTCVendor advisory
  53. 2026-06-08 09:27 UTCGHSA enrichment
  54. 2026-06-08 05:19 UTCVendor advisory
  55. 2026-06-08 05:19 UTCGHSA enrichment
  56. 2026-06-08 01:17 UTCVendor advisory
  57. 2026-06-08 01:17 UTCGHSA enrichment
  58. 2026-06-07 19:32 UTCVendor advisory
  59. 2026-06-07 19:32 UTCGHSA enrichment
  60. 2026-06-07 15:30 UTCVendor advisory
  61. 2026-06-07 15:30 UTCGHSA enrichment
  62. 2026-06-07 15:25 UTCEPSS rescore
  63. 2026-06-07 15:24 UTCEPSS rescore
  64. 2026-06-06 13:47 UTCEPSS rescore
  65. 2026-06-06 13:47 UTCEPSS rescore
  66. 2026-06-06 13:47 UTCEPSS rescore
  67. 2026-06-05 22:47 UTCEPSS rescore
  68. 2026-06-05 06:10 UTCEPSS rescore
  69. 2026-06-05 06:10 UTCEPSS rescore
  70. 2026-06-04 13:12 UTCEPSS rescore
  71. 2026-06-04 13:12 UTCEPSS rescore
  72. 2026-06-04 13:12 UTCEPSS rescore
  73. 2026-06-02 20:13 UTCEPSS rescore
  74. 2026-06-02 20:13 UTCEPSS rescore
  75. 2026-06-01 13:51 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-0848?
CVE-2026-0848 is a critical vulnerability published on March 5, 2026. NLTK versions <=3.9.2 are vulnerable to arbitrary code execution due to improper input validation in the StanfordSegmenter module. The module dynamically loads external Java .jar files without verification or sandboxing. An attacker can supply or replace the JAR file, enabling the execution of…
When was CVE-2026-0848 disclosed?
CVE-2026-0848 was first published in the National Vulnerability Database on March 5, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-0848 actively exploited?
CVE-2026-0848 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 46.9% of all scored CVEs.
What is the CVSS score of CVE-2026-0848?
CVE-2026-0848 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2026-0848?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-0848, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-0848

Explore →

Is Your Infrastructure Affected by CVE-2026-0848?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs