CVE-2022-36114

MEDIUMNVD 4.84.8
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 4.8 under NVD CVSS v3. EPSS exploit probability: 0.9% (60th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
4.8EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 4.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Cargo is a package manager for the rust programming language. It was discovered that Cargo did not limit the amount of data extracted from compressed archives. An attacker could upload to an alternate registry a specially crafted package that extracts way more data than its size (also known as a "zip bomb"), exhausting the disk space on the machine using Cargo to download the package. Note that by design Cargo allows code execution at build time, due to build scripts and procedural macros. The vulnerabilities in this advisory allow performing a subset of the possible damage in a harder to track down way. Your dependencies must still be trusted if you want to be protected from attacks, as it's possible to perform the same attacks with build scripts and procedural macros. The vulnerability is present in all versions of Cargo. Rust 1.64, to be released on September 22nd, will include a fix for it. Since the vulnerability is just a more limited way to accomplish what a malicious build scripts or procedural macros can do, we decided not to publish Rust point releases backporting the security fix. Patch files are available for Rust 1.63.0 are available in the wg-security-response repository for people building their own toolchain. We recommend users of alternate registries to excercise care in which package they download, by only including trusted dependencies in their projects. Please note that even with these vulnerabilities fixed, by design Cargo allows arbitrary code execution at build time thanks to build scripts and procedural macros: a malicious dependency will be able to cause damage regardless of these vulnerabilities. crates.io implemented server-side checks to reject these kinds of packages years ago, and there are no packages on crates.io exploiting these vulnerabilities. crates.io users still need to excercise care in choosing their dependencies though, as the same concerns about build scripts and procedural macros apply here.

CVSS v3
4.8
EG Score
4.8MEDIUMmedium confidence
EG Risk
22
EG Risk 22/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)
Severity48% × 45%
Impact severity (EG Severity): CVSS 4.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.9% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.
EPSS PROB
0.9%
EPSS %ILE
60th
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 (4.8): severity, escalated by confirmed exploitation. This CVE's 4.8 is its impact severity (EG Severity), not escalated.

EG Severity
4.8 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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 every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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 14, 2022

Last Modified

November 21, 2024

References (2)

Vendor Advisories for CVE-2022-36114(1)

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

Affected Packages

(7 across 5 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
cargo0.47.0-3 ... 0.70.1-1~exp1 (21 versions)
  • every version on: no fix on record
—
rust-cargo0.43.1-4 ... 0.91.0-4 (34 versions)
  • every version on: no fix on record
—
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
cargo—
  • every version up to 0.63.1-1: fixed in 0.63.1-1
—
rust-cargo—
  • every version up to 0.66.0-1: fixed in 0.66.0-1
—
crates.io(1)
PackageVulnerable rangeFix by version rangeDependents
cargo0.66.0
  • every version up to 0.65.0: fixed in 0.65.0
  • 0.66.0 up to 0.67.0: fixed in 0.67.0
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
rust-cargo—
  • every version up to 0.66.0-1: fixed in 0.66.0-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
rust-cargo—
  • every version up to 0.66.0-1: fixed in 0.66.0-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 34× 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 92 of 197 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. 8 repeat rows among the latest 100 are merged into the row they repeat. The 105 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2022-36114?
CVE-2022-36114 is a medium-severity vulnerability; its CVE record was published on September 14, 2022. Cargo is a package manager for the rust programming language. It was discovered that Cargo did not limit the amount of data extracted from compressed archives. An attacker could upload to an alternate registry a specially crafted package that extracts way more data than its size (also known as a…
When was the CVE record for CVE-2022-36114 published?
The CVE record for CVE-2022-36114 was published on September 14, 2022. 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 November 21, 2024; the record at its source may have been updated since.
Is CVE-2022-36114 actively exploited?
CVE-2022-36114 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (60th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-36114?
CVE-2022-36114 has a CVSS v3 base score of 4.8 (NVD).
How do I remediate CVE-2022-36114?
A fix for CVE-2022-36114 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-36114 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-2022-36114

Explore →

Is Your Infrastructure Affected by CVE-2022-36114?

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

Book a Demo →Browse All CVEs