CVE-2026-0848

CRITICALNVD 10.010.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

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, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-9875 (ENISA EUVD) · GHSA-v2w2-xcg6-53wj (GitHub Security Advisories)Source: ENISA EUVD

10.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 10.0Exploit: No code on recordExposed services: Not assessed

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.0CRITICALmedium confidence
EG Risk
76
EG Risk 76/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.8%
EPSS %ILE
57th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 5, 2026

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated Nov 1, 2026
Patch available.
Web page

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

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntupython3-nltk (3.1-1ubuntu0.1+esm4) @ xenial2026-11-02ubuntu

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
nltk3.10.0-1 ... 3.9.3-1 (12 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
nltk3.10.0-1 ... 3.9.3-1 (9 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
nltk3.10.0-1 ... 3.9.3-1 (6 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
nltk3.9.1-2, 3.9.2-1
  • every version up to 3.9.3-1: fixed in 3.9.3-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
nltk0.8 ... 3.9b1 (63 versions)
  • every version up to 3.9.3: fixed in 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 26× in last 7d / 91× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 347 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 247 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-0848?
CVE-2026-0848 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-0848 published?
The CVE record for CVE-2026-0848 was published on March 5, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-0848 actively exploited?
CVE-2026-0848 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (57th percentile of EPSS-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?
A fix for CVE-2026-0848 is available: update to the fixed version the vendor names in its advisory.

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.