CVE-2021-32751

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 2.7% (85th 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
Trending — 3 sources updated this week

Also known asEUVD-2021-19523 (ENISA EUVD)Source: ENISA EUVD

7.5EG
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).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2.7%CVSS: 7.5Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

Gradle is a build tool with a focus on build automation. In versions prior to 7.2, start scripts generated by the application plugin and the gradlew script are both vulnerable to arbitrary code execution when an attacker is able to change environment variables for the user running the script. This may impact those who use gradlew on Unix-like systems or use the scripts generated by Gradle in thieir application on Unix-like systems. For this vulnerability to be exploitable, an attacker needs to be able to set the value of particular environment variables and have those environment variables be seen by the vulnerable scripts. This issue has been patched in Gradle 7.2 by removing the use of eval and requiring the use of the bash shell. There are a few workarounds available. For CI/CD systems using the Gradle build tool, one may ensure that untrusted users are unable to change environment variables for the user that executes gradlew. If one is unable to upgrade to Gradle 7.2, one may generate a new gradlew script with Gradle 7.2 and use it for older versions of Gradle. Fpplications using start scripts generated by Gradle, one may ensure that untrusted users are unable to change environment variables for the user that executes the start script. A vulnerable start script could be manually patched to remove the use of eval or the use of environment variables that affect the application's command-line. If the application is simple enough, one may be able to avoid the use of the start scripts by running the application directly with Java command.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
50
EG Risk 50/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation2.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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: The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
2.7%
EPSS %ILE
85th
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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
2.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). 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, 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 or medium mission impact; Attend at high (mission-essential systems).

The CVE record names the fixed release. 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.

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

July 20, 2021

Last Modified

October 8, 2026

Advisory Details (2)

Auto-updated Oct 8, 2026
Fix named in the CVE record. Sources: github.
Web page

BashFAQ/048 - Greg's Wiki

https://mywiki.wooledge.org/BashFAQ/048
GitHub advisoryMentions a patch (unverified)

Arbitrary code execution via specially crafted environment variables · Advisory · gradle/gradle · GitHub

https://github.com/gradle/gradle/security/advisories/GHSA-6j2p-252f-7mw8

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
gradle4.4.1-13 ... 4.4.1-23 (11 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
gradle4.4.1-18 ... 4.6-3 (10 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
gradle4.4.1-22 ... 4.6-3 (6 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
gradle4.4.1-22 ... 4.6-3 (6 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 38× 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 210 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 116 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2021-32751?
CVE-2021-32751 is a high-severity vulnerability; its CVE record was published on July 20, 2021. Gradle is a build tool with a focus on build automation. In versions prior to 7.2, start scripts generated by the application plugin and the gradlew script are both vulnerable to arbitrary code execution when an attacker is able to change environment variables for the user running the script. This…
When was the CVE record for CVE-2021-32751 published?
The CVE record for CVE-2021-32751 was published on July 20, 2021. 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 October 8, 2026; the record at its source may have been updated since.
Is CVE-2021-32751 actively exploited?
CVE-2021-32751 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.7% probability of exploitation in the next 30 days (85th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2021-32751?
CVE-2021-32751 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2021-32751?
The CVE record for CVE-2021-32751 names the fix: "This issue has been patched in Gradle 7.2 by removing the use of `eval` and requiring the use of the `bash` shell."

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2021-32751

Explore →

Is Your Infrastructure Affected by CVE-2021-32751?

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

Book a Demo →Browse All CVEs