CVE-2018-1000802

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-13. NVD baseline CVSS 9.8; 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
9.8EG
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).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 20%CVSS: 9.8Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

Python Software Foundation Python (CPython) version 2.7 contains a CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability in shutil module (make_archive function) that can result in Denial of service, Information gain via injection of arbitrary files on the system or entire drive. This attack appear to be exploitable via Passage of unfiltered user input to the function. This vulnerability appears to have been fixed in after commit add531a1e55b0a739b0f42582f1c9747e5649ace.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 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 or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (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
20%
EPSS %ILE
97th
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
20% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-22). 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 or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

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

Exploitation none (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.

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

September 18, 2018

Last Modified

October 8, 2026

Advisory Details (7)

Auto-updated Oct 23, 2026
Patch available. Sources: github_pr.
Web pageMentions a patch (unverified)

[SECURITY] [DLA 1520-1] python3.4 security update

https://lists.debian.org/debian-lts-announce/2018/09/msg00031.html
Web pageMentions a patch (unverified)

[SECURITY] [DLA 1519-1] python2.7 security update

https://lists.debian.org/debian-lts-announce/2018/09/msg00030.html
GitHub pull request

[2.7] closes bpo-34540: Convert shutil._call_external_zip to use subprocess rather than distutils.spawn.

Fix merged in python/cpython PR #8985 on 2018-08-30 — awaiting tagged release

https://github.com/python/cpython/pull/8985/commits/add531a1e55b0a739b0f42582f1c9747e5649ace
GitHub pull request

[2.7] closes bpo-34540: Convert shutil._call_external_zip to use subprocess rather than distutils.spawn.

Fix merged in python/cpython PR #8985 on 2018-08-30 — awaiting tagged release

https://github.com/python/cpython/pull/8985
Web page

Issue 34540: shutil._call_external_zip should use subprocess - Python tracker

https://bugs.python.org/issue34540

Vendor Advisories for CVE-2018-1000802(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntupython2.7 (2.7.3-0ubuntu3.11) @ precise2026-10-21ubuntu
ubuntupython3.5-venv (3.5.2-2ubuntu0~16.04.5) @ xenial2026-10-21ubuntu

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

(4 across 3 ecosystems)
Debian:8(2)
PackageVulnerable rangeFix by version rangeDependents
python2.72.7.9-2, 2.7.9-2+deb8u1
  • every version up to 2.7.9-2+deb8u2: fixed in 2.7.9-2+deb8u2
—
python3.43.4.2-1
  • every version up to 3.4.2-1+deb8u1: fixed in 3.4.2-1+deb8u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
python2.7—
  • every version up to 2.7.15-5: fixed in 2.7.15-5
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
python2.72.7.13-2, 2.7.13-2+deb9u1, 2.7.13-2+deb9u2
  • every version up to 2.7.13-2+deb9u3: fixed in 2.7.13-2+deb9u3
—

Weakness Classification(1)

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

All Vendor Advisories

(2)

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 24× in last 7d / 56× 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 94 of 180 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. 6 repeat rows among the latest 100 are merged into the row they repeat. The 86 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • GitHub PoCtna0y/CVE-2018-1000802-PoC
    Published Sep 14, 2018

    Python CVE-2018-1000802 Proof-of-Concept

    Open source ↗

Frequently asked(5)

What is CVE-2018-1000802?
CVE-2018-1000802 is a critical-severity vulnerability; its CVE record was published on September 18, 2018. Python Software Foundation Python (CPython) version 2.7 contains a CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability in shutil module (make_archive function) that can result in Denial of service, Information gain via injection of arbitrary…
When was CVE-2018-1000802 made public?
CVE-2018-1000802 was made public on August 29, 2018: that is the date its CVE record's CNA, MITRE Corporation, gives for when the vulnerability was made public. The CVE record itself was published on September 18, 2018. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2018-1000802 actively exploited?
CVE-2018-1000802 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 20% probability of exploitation in the next 30 days (97th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2018-1000802?
CVE-2018-1000802 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2018-1000802?
A fix for CVE-2018-1000802 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2018-1000802 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2018-1000802

Explore →

Is Your Infrastructure Affected by CVE-2018-1000802?

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