CVE-2022-24441

HIGHNVD 5.88.8
EchelonGraph scoreMEDIUM confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2023-07-06. NVD baseline CVSS 5.8; sources differ by 3.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2023-1960 (ENISA EUVD) · GHSA-4vrv-93c7-m92j (GitHub Security Advisories)Source: ENISA EUVD

8.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.8%CVSS: 5.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The package snyk before 1.1064.0 are vulnerable to Code Injection when analyzing a project. An attacker who can convince a user to scan a malicious project can include commands in a build file such as build.gradle or gradle-wrapper.jar, which will be executed with the privileges of the application. This vulnerability may be triggered when running the the CLI tool directly, or when running a scan with one of the IDE plugins that invoke the Snyk CLI. Successful exploitation of this issue would likely require some level of social engineering - to coerce an untrusted project to be downloaded and analyzed via the Snyk CLI or opened in an IDE where a Snyk IDE plugin is installed and enabled. Additionally, if the IDE has a Trust feature then the target folder must be marked as ‘trusted’ in order to be vulnerable. NOTE: This issue is independent of the one reported in CVE-2022-40764, and upgrading to a fixed version for this addresses that issue as well. The affected IDE plugins and versions are: - VS Code - Affected: <=1.8.0, Fixed: 1.9.0 - IntelliJ - Affected: <=2.4.47, Fixed: 2.4.48 - Visual Studio - Affected: <=1.1.30, Fixed: 1.1.31 - Eclipse - Affected: <=v20221115.132308, Fixed: All subsequent versions - Language Server - Affected: <=v20221109.114426, Fixed: All subsequent versions

CVSS v3
5.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/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)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.8% × 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.8%
EPSS %ILE
56th
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 (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-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-08). 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, and whom BOD 26-04 binds: 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.

The score's inputs: 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

November 30, 2022

Last Modified

April 24, 2025

Advisory Details (7)

Auto-updated Nov 8, 2026
Patch available. Sources: github_commit.
GitHub commit

commit b3229f0142f7 (snyk/snyk-ls)

Fix landed in snyk/snyk-ls commit b3229f0142f7 — awaiting tagged release

https://github.com/snyk/snyk-ls/commit/b3229f0142f782871aa72d1a7dcf417546d568ed
GitHub commit Patch Available

commit 56682f4ba608 (snyk/snyk-intellij-plugin)

Patch available: snyk/snyk-intellij-plugin v2.8.5 (contains commit 56682f4ba608)

https://github.com/snyk/snyk-intellij-plugin/commit/56682f4ba6081ce1d95cb980cbfacd3809a826f4
GitHub commit Patch Available

commit b5a8bce25a35 (snyk/snyk-eclipse-plugin)

Patch available: snyk/snyk-eclipse-plugin v20231129.123319 (contains commit b5a8bce25a35)

https://github.com/snyk/snyk-eclipse-plugin/commit/b5a8bce25a359ced75f83a729fc6b2393fc9a495
Web page

How Scanning Your Projects for Security Issues Can Lead to Remote Code Execution | Imperva

https://www.imperva.com/blog/how-scanning-your-projects-for-security-issues-can-lead-to-remote-code-execution/
Web page

Code Injection in snyk | CVE-2022-24441 | Snyk

https://security.snyk.io/vuln/SNYK-JS-SNYK-3111871
GitHub commit Patch Available

commit 0db3b4240be0 (snyk/vscode-extension)

Patch available: snyk/vscode-extension v2.14.0 (contains commit 0db3b4240be0)

https://github.com/snyk/vscode-extension/commit/0db3b4240be0db6a0a5c6d02c0d4231a2c4ba708
GitHub commit Patch Available

commit 0b53dbbd4a31 (snyk/snyk-visual-studio-plugin)

Patch available: snyk/snyk-visual-studio-plugin 1.1.53 (contains commit 0b53dbbd4a31)

https://github.com/snyk/snyk-visual-studio-plugin/commit/0b53dbbd4a3153c3ef9aaf797af3b5caad0f731a

Vendor Advisories for CVE-2022-24441(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmsnyk @ 1.1064.0 (fixes < 1.1064.0)—ghsa

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)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
snyk—
  • every version up to 1.1064.0: fixed in 1.1064.0
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 33× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 214 rows on record for this CVE, as 98 entries (2 repeats merged).

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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 114 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 16:29 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  2. 2026-11-11 16:32 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  3. 2026-11-10 16:35 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  4. 2026-11-09 16:29 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  5. 2026-11-08 19:31 UTCEchelonGraph re-scored
  6. 2026-11-08 19:31 UTCGHSA enrichmentGHSA-4vrv-93c7-m92j · GitHub severity HIGH · GitHub CVSS 8.8
  7. 2026-11-08 16:33 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  8. 2026-11-07 16:34 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  9. 2026-11-06 16:30 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  10. 2026-11-05 16:31 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  11. 2026-11-04 16:30 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  12. 2026-11-03 16:39 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  13. 2026-11-02 16:38 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  14. 2026-11-01 16:30 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  15. 2026-11-01 08:28 UTCGHSA enrichmentGHSA-4vrv-93c7-m92j · GitHub severity HIGH · GitHub CVSS 8.8
  16. 2026-11-01 08:28 UTCEchelonGraph re-scored▲ 3.00
  17. 2026-10-31 16:29 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  18. 2026-10-30 16:30 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  19. 2026-10-29 16:29 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  20. 2026-10-28 16:28 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  21. 2026-10-27 16:28 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  22. 2026-10-26 16:28 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  23. 2026-10-25 18:12 UTCEchelonGraph re-scored
  24. 2026-10-25 16:29 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  25. 2026-10-24 20:41 UTCEchelonGraph re-scored
Show 73 more
  1. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  2. 2026-10-23 16:28 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  3. 2026-10-22 16:30 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  4. 2026-10-21 16:28 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  5. 2026-10-20 16:29 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  6. 2026-10-19 16:28 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  7. 2026-10-18 16:28 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  8. 2026-10-18 08:41 UTCEchelonGraph re-scored
  9. 2026-10-17 16:29 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  10. 2026-10-16 16:34 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  11. 2026-10-15 16:28 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  12. 2026-10-15 08:54 UTCOSV refresh
  13. 2026-10-14 16:29 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  14. 2026-10-13 16:29 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  15. 2026-10-12 18:59 UTCEchelonGraph re-scored
  16. 2026-10-12 16:30 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  17. 2026-10-11 23:24 UTCEchelonGraph re-scored
  18. 2026-10-11 13:44 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  19. 2026-10-10 19:56 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  20. 2026-10-09 20:04 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  21. 2026-10-08 16:40 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  22. 2026-10-07 23:45 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  23. 2026-10-06 15:14 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  24. 2026-10-05 17:40 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  25. 2026-10-04 23:19 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  26. 2026-10-03 14:22 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  27. 2026-09-30 15:51 UTCEchelonGraph re-scored
  28. 2026-09-30 15:00 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  29. 2026-09-29 15:15 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  30. 2026-09-28 13:48 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  31. 2026-09-27 13:41 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  32. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  33. 2026-09-24 14:00 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  34. 2026-09-24 04:45 UTCOSV refresh
  35. 2026-09-23 13:45 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  36. 2026-09-20 20:13 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  37. 2026-09-17 19:23 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  38. 2026-09-16 14:05 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  39. 2026-09-15 03:06 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  40. 2026-09-12 14:57 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  41. 2026-09-11 14:49 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  42. 2026-09-11 09:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  43. 2026-09-08 21:57 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  44. 2026-09-07 15:58 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  45. 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  46. 2026-09-05 15:25 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  47. 2026-09-04 21:59 UTCOSV refresh
  48. 2026-09-04 13:57 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  49. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  50. 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  51. 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  52. 2026-08-30 19:14 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  53. 2026-08-30 01:19 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  54. 2026-08-28 21:38 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  55. 2026-08-27 14:22 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  56. 2026-08-26 14:43 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  57. 2026-08-25 13:46 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  58. 2026-08-24 14:13 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  59. 2026-08-21 23:46 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  60. 2026-08-20 22:52 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  61. 2026-08-19 17:01 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  62. 2026-08-18 13:45 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  63. 2026-08-18 09:22 UTCOSV refresh
  64. 2026-08-17 13:44 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  65. 2026-08-16 14:53 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  66. 2026-08-16 02:11 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  67. 2026-08-15 01:27 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  68. 2026-08-13 21:57 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  69. 2026-08-12 13:48 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  70. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  71. 2026-08-08 16:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  72. 2026-08-07 16:24 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  73. 2026-08-06 13:44 UTCEPSS rescoreEPSS 0.7% · 50th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2022-24441?
CVE-2022-24441 is a high-severity vulnerability; its CVE record was published on November 30, 2022. The package snyk before 1.1064.0 are vulnerable to Code Injection when analyzing a project. An attacker who can convince a user to scan a malicious project can include commands in a build file such as build.gradle or gradle-wrapper.jar, which will be executed with the privileges of the application.…
When was CVE-2022-24441 made public?
CVE-2022-24441 was made public on November 30, 2022: that is the date its CVE record's CNA, Snyk, gives for when the vulnerability was made public. The CVE record itself was published on November 30, 2022. EchelonGraph's copy of the record carries a last-modified date of April 24, 2025; the record at its source may have been updated since.
Is CVE-2022-24441 actively exploited?
CVE-2022-24441 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (56th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-24441?
CVE-2022-24441 has a CVSS v3 base score of 5.8 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 8.8 (HIGH).
How do I remediate CVE-2022-24441?
A fix for CVE-2022-24441 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-24441 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-24441

Explore →

Is Your Infrastructure Affected by CVE-2022-24441?

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

Book a Demo →Browse All CVEs