2017-2026 · Updated November 2026
A decade of package CVEs
Ten years of vulnerabilities in open source packages from the ShieldedStack advisory database, by year, ecosystem, kind of flaw and severity, with each year's top 10 and a section on malicious packages.
Key findings
- 33,039 CVEs reached a package in npm, PyPI, Maven, Go, NuGet, crates.io, Packagist, RubyGems, Hex, Swift or GitHub Actions between January 2017 and November 2026.
- 12,154 package CVEs in 2026 by 18 November, against 3,454 in all of 2025. All CVEs roughly doubled.
- Broken access control overtook cross-site scripting in 2024 and is now 25% of package CVEs.
- 46% of Rust vulnerabilities published in 2026 have no CVE.
- 140,728 of 2025's 192,715 malicious-package reports came from one token-farming campaign. At least 1,158 legitimate packages were taken over.
CVEs affecting open source packages, 2017 to 18 Nov 2026
Source: ShieldedStack advisory database
package CVEs published in 2026 so far
Source: ShieldedStack advisory database
2026 to date against all of 2025
Source: ShieldedStack advisory database
malicious-package reports since 2022
Source: ShieldedStack advisory database
Per year
How many package CVEs are published each year?
The count roughly quadrupled between 2017 and 2022, from 818 to 3,235, then held near 3,000 a year through 2025. By 18 November 2026 there were 12,154, 3.5 times the whole of 2025.
Show as table
| Year | CVEs | On KEV |
|---|---|---|
| 2017 | 818 | 8 |
| 2018 | 1,615 | 10 |
| 2019 | 1,593 | 10 |
| 2020 | 1,945 | 18 |
| 2021 | 2,276 | 14 |
| 2022 | 3,235 | 9 |
| 2023 | 3,062 | 10 |
| 2024 | 2,887 | 5 |
| 2025 | 3,454 | 20 |
| 2026 | 12,154 | 17 |
2025 averaged 288 CVEs a month. January and February 2026 were busier (467 and 668), and from March the count settled at about 1,330 a month, 4.6 times the 2025 rate. NVD as a whole published 97,834 CVEs in 2026 so far against 48,150 in 2025. Packages went from 7% of all CVEs in 2025 to 12% in 2026.
Show as table
| Month | CVEs |
|---|---|
| 2017-01 | 54 |
| 2017-02 | 34 |
| 2017-03 | 64 |
| 2017-04 | 73 |
| 2017-05 | 68 |
| 2017-06 | 35 |
| 2017-07 | 67 |
| 2017-08 | 93 |
| 2017-09 | 83 |
| 2017-10 | 108 |
| 2017-11 | 94 |
| 2017-12 | 45 |
| 2018-01 | 149 |
| 2018-02 | 80 |
| 2018-03 | 109 |
| 2018-04 | 76 |
| 2018-05 | 168 |
| 2018-06 | 471 |
| 2018-07 | 137 |
| 2018-08 | 106 |
| 2018-09 | 81 |
| 2018-10 | 73 |
| 2018-11 | 70 |
| 2018-12 | 95 |
| 2019-01 | 98 |
| 2019-02 | 74 |
| 2019-03 | 95 |
| 2019-04 | 205 |
| 2019-05 | 87 |
| 2019-06 | 72 |
| 2019-07 | 140 |
| 2019-08 | 221 |
| 2019-09 | 154 |
| 2019-10 | 139 |
| 2019-11 | 192 |
| 2019-12 | 116 |
| 2020-01 | 167 |
| 2020-02 | 127 |
| 2020-03 | 210 |
| 2020-04 | 119 |
| 2020-05 | 125 |
| 2020-06 | 227 |
| 2020-07 | 164 |
| 2020-08 | 89 |
| 2020-09 | 208 |
| 2020-10 | 119 |
| 2020-11 | 155 |
| 2020-12 | 235 |
| 2021-01 | 182 |
| 2021-02 | 183 |
| 2021-03 | 207 |
| 2021-04 | 168 |
| 2021-05 | 267 |
| 2021-06 | 161 |
| 2021-07 | 100 |
| 2021-08 | 308 |
| 2021-09 | 160 |
| 2021-10 | 129 |
| 2021-11 | 207 |
| 2021-12 | 204 |
| 2022-01 | 238 |
| 2022-02 | 318 |
| 2022-03 | 327 |
| 2022-04 | 182 |
| 2022-05 | 244 |
| 2022-06 | 305 |
| 2022-07 | 212 |
| 2022-08 | 220 |
| 2022-09 | 362 |
| 2022-10 | 206 |
| 2022-11 | 285 |
| 2022-12 | 336 |
| 2023-01 | 255 |
| 2023-02 | 240 |
| 2023-03 | 324 |
| 2023-04 | 302 |
| 2023-05 | 239 |
| 2023-06 | 243 |
| 2023-07 | 234 |
| 2023-08 | 218 |
| 2023-09 | 254 |
| 2023-10 | 248 |
| 2023-11 | 238 |
| 2023-12 | 267 |
| 2024-01 | 247 |
| 2024-02 | 283 |
| 2024-03 | 272 |
| 2024-04 | 246 |
| 2024-05 | 255 |
| 2024-06 | 216 |
| 2024-07 | 245 |
| 2024-08 | 208 |
| 2024-09 | 211 |
| 2024-10 | 286 |
| 2024-11 | 247 |
| 2024-12 | 171 |
| 2025-01 | 268 |
| 2025-02 | 184 |
| 2025-03 | 402 |
| 2025-04 | 272 |
| 2025-05 | 242 |
| 2025-06 | 254 |
| 2025-07 | 261 |
| 2025-08 | 295 |
| 2025-09 | 344 |
| 2025-10 | 363 |
| 2025-11 | 234 |
| 2025-12 | 335 |
| 2026-01 | 467 |
| 2026-02 | 668 |
| 2026-03 | 1,355 |
| 2026-04 | 1,267 |
| 2026-05 | 1,421 |
| 2026-06 | 1,361 |
| 2026-07 | 1,348 |
| 2026-08 | 1,365 |
| 2026-09 | 1,186 |
| 2026-10 | 1,333 |
| 2026-11 | 383 |
The spike in June 2018 is 193 npm CVEs published on 7 June, mostly path traversal (CWE-22), with some malicious packages (CWE-506).
Ecosystems
Which package ecosystems carry the most CVEs?
npm went from 542 to 3,312 (6.1x), PyPI 3.6x and Go 3.4x, while Maven, the largest ecosystem in most years before 2024, grew only 1.5x. Hex went from 9 CVEs to 320.
| Ecosystem | 2017 | 2018 | 2019 | 2020 | 2021 | 2022 | 2023 | 2024 | 2025 | 2026 | 2026 vs 2025 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| npm | 56 | 549 | 150 | 365 | 418 | 464 | 362 | 394 | 542 | 3,312 | 6.1x |
| Maven | 290 | 467 | 592 | 552 | 497 | 936 | 917 | 529 | 671 | 1,023 | 1.5x |
| PyPI | 158 | 142 | 182 | 249 | 479 | 556 | 515 | 678 | 729 | 2,606 | 3.6x |
| Packagist (PHP) | 192 | 232 | 397 | 317 | 420 | 671 | 649 | 550 | 643 | 1,701 | 2.6x |
| Go | 28 | 48 | 81 | 243 | 174 | 442 | 467 | 533 | 649 | 2,193 | 3.4x |
| crates.io (Rust) | 1 | 1 | 43 | 106 | 222 | 70 | 66 | 83 | 118 | 473 | 4.0x |
| NuGet | 50 | 122 | 98 | 70 | 34 | 55 | 61 | 92 | 91 | 403 | 4.4x |
| RubyGems | 57 | 84 | 76 | 68 | 69 | 80 | 69 | 89 | 58 | 229 | 3.9x |
| Hex (Erlang/Elixir) | 4 | 3 | 5 | 2 | 1 | 2 | 7 | 5 | 9 | 320 | 35.6x |
| Swift | 0 | 0 | 0 | 0 | 0 | 0 | 4 | 1 | 6 | 1 | 0.2x |
| GitHub Actions | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 8 | new |
Without a CVE
What do CVE counts miss?
Some vulnerabilities never get a CVE and are published only as a GitHub, RustSec, Go, PyPA or Drupal advisory. Since 2017 about 3,726 package vulnerabilities have had no CVE, about 11% on top of the CVE count. In most ecosystems they are a small share, at most 6% in 2026. In Rust, 409 of 882 crates.io vulnerabilities published in 2026 (46%) have no CVE.
| Ecosystem | With a CVE | Without | Share without |
|---|---|---|---|
| crates.io (Rust) | 473 | 409 | 46% |
| Go | 2,193 | 150 | 6% |
| PyPI | 2,606 | 151 | 5% |
| npm | 3,312 | 216 | 6% |
| NuGet | 403 | 25 | 6% |
| RubyGems | 229 | 12 | 5% |
| Packagist (PHP) | 1,701 | 53 | 3% |
| Maven | 1,023 | 21 | 2% |
| Hex (Erlang/Elixir) | 320 | 0 | 0% |
Kinds of flaw
Which kinds of flaws dominate package CVEs?
Cross-site scripting was the largest category in every year from 2017 to 2023 except 2018, when the June batch of npm path traversal CVEs put path traversal briefly ahead. In 2024 broken access control and authentication overtook it, and in 2026 it accounts for 25% of package CVEs, against 8% for XSS, less than half its 2023 share. Resource exhaustion (denial of service, ReDoS, decompression bombs) has risen from 3% of CVEs in 2017 to 14% and is now second.
Show as table
| Category | 2017 | 2018 | 2019 | 2020 | 2021 | 2022 | 2023 | 2024 | 2025 | 2026 |
|---|---|---|---|---|---|---|---|---|---|---|
| Access control & auth | 12.1% (99) | 8.5% (138) | 16.6% (265) | 13.3% (259) | 11.0% (251) | 16.8% (544) | 16.8% (515) | 18.0% (519) | 19.5% (674) | 25.5% (3095) |
| Cross-site scripting | 18.1% (148) | 13.7% (221) | 18.3% (291) | 15.3% (297) | 14.6% (332) | 19.2% (620) | 18.3% (561) | 16.3% (472) | 14.4% (498) | 7.8% (950) |
| Injection | 7.0% (57) | 6.3% (101) | 8.0% (128) | 12.0% (234) | 9.6% (219) | 9.1% (296) | 12.7% (389) | 11.3% (326) | 9.1% (314) | 10.5% (1282) |
| Resource exhaustion (DoS) | 2.9% (24) | 5.1% (83) | 3.4% (54) | 3.8% (74) | 9.3% (212) | 8.9% (287) | 8.3% (253) | 8.9% (256) | 10.3% (356) | 13.7% (1663) |
| Path traversal & files | 5.1% (42) | 14.0% (226) | 5.4% (86) | 5.4% (106) | 6.7% (152) | 7.4% (240) | 7.2% (220) | 9.0% (259) | 8.0% (276) | 9.3% (1131) |
| Memory safety | 7.2% (59) | 7.7% (124) | 7.8% (124) | 7.6% (148) | 13.3% (302) | 5.7% (186) | 4.2% (129) | 4.1% (118) | 4.6% (158) | 4.4% (538) |
Memory safety peaked at 13% in 2021 and has stayed between 4% and 6% since 2022. In 2026 the most common single CWEs after XSS are path traversal (CWE-22), incorrect authorization (CWE-863), SSRF (CWE-918) and missing authorization (CWE-862).
Severity
Are package CVEs getting more severe?
Critical and high together fell from 60% of 2017's CVEs to 41% of 2025's, while low-severity CVEs grew from 1% to 10%. In 2026 the share went back up, to 51% of a much larger count.
Show as table
| Year | Critical | High | Medium | Low |
|---|---|---|---|---|
| 2017 | 144 | 346 | 318 | 10 |
| 2018 | 191 | 834 | 572 | 18 |
| 2019 | 236 | 605 | 728 | 24 |
| 2020 | 349 | 669 | 873 | 54 |
| 2021 | 360 | 811 | 962 | 143 |
| 2022 | 478 | 1,115 | 1,527 | 113 |
| 2023 | 467 | 1,036 | 1,382 | 175 |
| 2024 | 367 | 996 | 1,324 | 195 |
| 2025 | 361 | 1,052 | 1,687 | 351 |
| 2026 | 1,344 | 4,847 | 5,002 | 931 |
Top 10
Which package CVEs mattered most each year?
Each year's critical CVEs (CVSS 9.0 or higher), ranked first by whether attackers have exploited them, marked KEV when the CVE is in CISA's Known Exploited Vulnerabilities catalogue. Next comes reach: how many package ecosystems and Linux distributions ship the affected code, then how many packages. The CVSS score breaks the remaining ties. Reach favours code bundled almost everywhere, such as the Go standard library or Tomcat, because a flaw there lands in more software.
1CVE-2025-24813Maven · org.apache.tomcat.embed:tomcat-embed-core +1 more12Ecosystems150Packages9.8CVSS 3.1KEV
Path Equivalence: 'file.Name' (Internal Dot) leading to Remote Code Execution and/or Information disclosure and/or malicious content added to uploaded files via write enabled Default Servlet in Apache Tomcat. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.2, from 10.1.0-M1 through 10.1.34, from 9.0.0.M1 through 9.0.98. The following versions were EOL at the time the CVE was created but are known to be affected: 8.5.0 though 8.5.100. Other, older, EOL versions may also be affected. If all of the following were true, a malicious user was able to view security sensitive files and/or inject content into those files: - writes enabled for the default servlet (disabled by default) - support for partial PUT (enabled by default) - a target URL for security sensitive uploads that was a sub-directory of a target URL for public uploads - attacker knowledge of the names of security sensitive files being uploaded - the security sensitive files also being uploaded via partial PUT If all of the following were true, a malicious user was able to perform remote code execution: - writes enabled for the default servlet (disabled by default) - support for partial PUT (enabled by default) - application was using Tomcat's file based session persistence with the default storage location - application included a library that may be leveraged in a deserialization attack Users are recommended to upgrade to version 11.0.3, 10.1.35 or 9.0.99, which fixes the issue.
- Published
- 2025-03-10
- CVSS
- 9.8 critical, scored by NVD ·
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Shipped in
- AlmaLinux, Amazon Linux, Chainguard, Debian, Maven, Oracle Linux, Red Hat, Rocky Linux, SUSE, Ubuntu, Wolfi, openSUSE (150 packages)
- KEV
- Added 2025-04-01
- EPSS today
- 99.9% (percentile 99.97)
- Weakness
- CWE-44, CWE-502, CWE-706 (Unsafe deserialization)
- Advisories
- GHSA-83qj-6fr2-vhqg
| Ecosystem | Package | Fixed in |
|---|---|---|
| Maven | org.apache.tomcat.embed:tomcat-embed-core | 9.0.99, 10.1.35, 11.0.3 |
| Maven | org.apache.tomcat:tomcat-catalina | 9.0.99, 10.1.35, 11.0.3 |
2CVE-2025-49113Packagist · roundcube/roundcubemail4Ecosystems4Packages9.9CVSS 3.1KEV
Roundcube Webmail before 1.5.10 and 1.6.x before 1.6.11 allows remote code execution by authenticated users because the _from parameter in a URL is not validated in program/actions/settings/upload.php, leading to PHP Object Deserialization.
- Published
- 2025-06-02
- CVSS
- 9.9 critical, scored by the CNA ·
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H - Shipped in
- Debian, Packagist, Ubuntu, openSUSE (4 packages)
- KEV
- Added 2026-02-20
- EPSS today
- 99.6% (percentile 99.95)
- Weakness
- CWE-502 (Unsafe deserialization)
- Advisories
- GHSA-8j8w-wwqc-x596
| Ecosystem | Package | Fixed in |
|---|---|---|
| Packagist | roundcube/roundcubemail | 1.5.10, 1.6.11 |
3CVE-2025-62593PyPI · ray3Ecosystems8Packages9.4CVSS 4.0KEV
Ray is an AI compute engine. Prior to version 2.52.0, developers working with Ray as a development tool can be exploited via a critical RCE vulnerability exploitable via Firefox and Safari. This vulnerability is due to an insufficient guard against browser-based attacks, as the current defense uses the User-Agent header starting with the string "Mozilla" as a defense mechanism. This defense is insufficient as the fetch specification allows the User-Agent header to be modified. Combined with a DNS rebinding attack against the browser, and this vulnerability is exploitable against a developer running Ray who inadvertently visits a malicious website, or is served a malicious advertisement (malvertising). This issue has been patched in version 2.52.0.
- Published
- 2025-11-26
- CVSS
- 9.4 critical, scored by the CNA ·
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X - Shipped in
- Chainguard, PyPI, Wolfi (8 packages)
- KEV
- Added 2026-08-17
- EPSS today
- 60.2% (percentile 99.15)
- Weakness
- CWE-94, CWE-352 (CSRF, Injection (SQL, command, code, template))
- Advisories
- GHSA-q279-jhrf-cc6v, PYSEC-2026-520
| Ecosystem | Package | Fixed in |
|---|---|---|
| PyPI | ray | 2.52.0 |
4CVE-2025-24016Go · github.com/wazuh/wazuh2Ecosystems2Packages9.9CVSS 3.1KEV
Wazuh is a free and open source platform used for threat prevention, detection, and response. Starting in version 4.4.0 and prior to version 4.9.1, an unsafe deserialization vulnerability allows for remote code execution on Wazuh servers. DistributedAPI parameters are a serialized as JSON and deserialized using `as_wazuh_object` (in `framework/wazuh/core/cluster/common.py`). If an attacker manages to inject an unsanitized dictionary in DAPI request/response, they can forge an unhandled exception (`__unhandled_exc__`) to evaluate arbitrary python code. The vulnerability can be triggered by anybody with API access (compromised dashboard or Wazuh servers in the cluster) or, in certain configurations, even by a compromised agent. Version 4.9.1 contains a fix.
- Published
- 2025-02-10
- CVSS
- 9.9 critical, scored by the CNA ·
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:H - Shipped in
- Go, openSUSE (2 packages)
- KEV
- Added 2025-06-10
- EPSS today
- 93.8% (percentile 99.85)
- Weakness
- CWE-502 (Unsafe deserialization)
- Advisories
- GHSA-hcrc-79hj-m3qh, GO-2025-3459
| Ecosystem | Package | Fixed in |
|---|---|---|
| Go | github.com/wazuh/wazuh | 4.9.1, 4.9.1+incompatible |
5CVE-2025-55182npm · react-server-dom-parcel +2 more1Ecosystems3Packages10.0CVSS 3.1KEV
A pre-authentication remote code execution vulnerability exists in React Server Components versions 19.0.0, 19.1.0, 19.1.1, and 19.2.0 including the following packages: react-server-dom-parcel, react-server-dom-turbopack, and react-server-dom-webpack. The vulnerable code unsafely deserializes payloads from HTTP requests to Server Function endpoints.
- Published
- 2025-12-03
- CVSS
- 10.0 critical, scored by the CNA ·
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H - Shipped in
- npm (3 packages)
- KEV
- Added 2025-12-05, known ransomware use
- EPSS today
- 99.7% (percentile 99.95)
- Weakness
- CWE-502 (Unsafe deserialization)
- Advisories
- GHSA-fv66-9v8q-g76r
| Ecosystem | Package | Fixed in |
|---|---|---|
| npm | react-server-dom-parcel | 19.0.1, 19.1.2, 19.2.1 |
| npm | react-server-dom-turbopack | 19.0.1, 19.1.2, 19.2.1 |
| npm | react-server-dom-webpack | 19.0.1, 19.1.2, 19.2.1 |
6CVE-2025-11953npm · @react-native-community/cli +1 more1Ecosystems2Packages9.8CVSS 3.1KEV
The Metro Development Server, which is opened by the React Native Community CLI, binds to external interfaces by default. The server exposes an endpoint that is vulnerable to OS command injection. This allows unauthenticated network attackers to send a POST request to the server and run arbitrary executables. On Windows, the attackers can also execute arbitrary shell commands with fully controlled arguments.
- Published
- 2025-11-03
- CVSS
- 9.8 critical, scored by the CNA ·
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Shipped in
- npm (2 packages)
- KEV
- Added 2026-02-05
- EPSS today
- 94.0% (percentile 99.85)
- Weakness
- CWE-78 (Injection (SQL, command, code, template))
- Advisories
- GHSA-399j-vxmf-hjvr
| Ecosystem | Package | Fixed in |
|---|---|---|
| npm | @react-native-community/cli | 18.0.1, 19.1.2, 20.0.0 |
| npm | @react-native-community/cli-server-api | 18.0.1, 19.1.2, 20.0.0 |
7CVE-2025-3248PyPI · langflow +1 more1Ecosystems2Packages9.8CVSS 3.1KEV
Langflow versions prior to 1.3.0 are susceptible to code injection in the /api/v1/validate/code endpoint. A remote and unauthenticated attacker can send crafted HTTP requests to execute arbitrary code.
- Published
- 2025-04-07
- CVSS
- 9.8 critical, scored by the CNA ·
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Shipped in
- PyPI (2 packages)
- KEV
- Added 2025-05-05, known ransomware use
- EPSS today
- 100.0% (percentile 99.99)
- Weakness
- CWE-306, CWE-94 (Broken access control & auth, Injection (SQL, command, code, template))
- Advisories
- GHSA-rvqx-wpfh-mfx7, PYSEC-2025-36, PYSEC-2026-380
| Ecosystem | Package | Fixed in |
|---|---|---|
| PyPI | langflow | 1.3.0 |
| PyPI | langflow-base | 0.3.0 |
8CVE-2025-54236Packagist · magento/community-edition +1 more1Ecosystems2Packages9.1CVSS 3.1KEV
Adobe Commerce versions 2.4.9-alpha2, 2.4.8-p2, 2.4.7-p7, 2.4.6-p12, 2.4.5-p14, 2.4.4-p15 and earlier are affected by an Improper Input Validation vulnerability. A successful attacker can abuse this to achieve session takeover, increasing the confidentiality, and integrity impact to high. Exploitation of this issue does not require user interaction.
- Published
- 2025-09-09
- CVSS
- 9.1 critical, scored by the CNA ·
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N - Shipped in
- Packagist (2 packages)
- KEV
- Added 2025-10-24
- EPSS today
- 95.5% (percentile 99.87)
- Weakness
- CWE-20 (Improper input validation)
- Advisories
- GHSA-wh92-6q6g-px7j
| Ecosystem | Package | Fixed in |
|---|---|---|
| Packagist | magento/community-edition | No fixed version listed |
| Packagist | magento/project-community-edition | No fixed version listed |
9CVE-2025-32432Packagist · craftcms/cms1Ecosystems1Packages10.0CVSS 3.1KEV
Craft is a flexible, user-friendly CMS for creating custom digital experiences on the web and beyond. Starting from version 3.0.0-RC1 to before 3.9.15, 4.0.0-RC1 to before 4.14.15, and 5.0.0-RC1 to before 5.6.17, Craft is vulnerable to remote code execution. This is a high-impact, low-complexity attack vector. This issue has been patched in versions 3.9.15, 4.14.15, and 5.6.17, and is an additional fix for CVE-2023-41892.
- Published
- 2025-04-25
- CVSS
- 10.0 critical, scored by the CNA ·
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L - Shipped in
- Packagist (1 packages)
- KEV
- Added 2026-03-20
- EPSS today
- 99.8% (percentile 99.96)
- Weakness
- CWE-94 (Injection (SQL, command, code, template))
- Advisories
- GHSA-f3gw-9ww9-jmc3
| Ecosystem | Package | Fixed in |
|---|---|---|
| Packagist | craftcms/cms | 3.9.15, 4.14.15, 5.6.17 |
10CVE-2025-68613npm · n8n1Ecosystems1Packages9.9CVSS 3.1KEV
n8n is an open source workflow automation platform. Versions starting with 0.211.0 and prior to 1.120.4, 1.121.1, and 1.122.0 contain a critical Remote Code Execution (RCE) vulnerability in their workflow expression evaluation system. Under certain conditions, expressions supplied by authenticated users during workflow configuration may be evaluated in an execution context that is not sufficiently isolated from the underlying runtime. An authenticated attacker could abuse this behavior to execute arbitrary code with the privileges of the n8n process. Successful exploitation may lead to full compromise of the affected instance, including unauthorized access to sensitive data, modification of workflows, and execution of system-level operations. This issue has been fixed in versions 1.120.4, 1.121.1, and 1.122.0. Users are strongly advised to upgrade to a patched version, which introduces additional safeguards to restrict expression evaluation. If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Limit workflow creation and editing permissions to fully trusted users only; and/or deploy n8n in a hardened environment with restricted operating system privileges and network access to reduce the impact of potential exploitation. These workarounds do not fully eliminate the risk and should only be used as short-term measures.
- Published
- 2025-12-19
- CVSS
- 9.9 critical, scored by the CNA ·
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H - Shipped in
- npm (1 packages)
- KEV
- Added 2026-03-11
- EPSS today
- 99.0% (percentile 99.93)
- Weakness
- CWE-913
- Advisories
- GHSA-v98v-ff95-f3cp
| Ecosystem | Package | Fixed in |
|---|---|---|
| npm | n8n | 1.120.4, 1.121.1 |
Malicious packages
How fast are malicious packages growing?
Alongside vulnerabilities, we track 241,252 reports of malicious packages from the OpenSSF Malicious Packages collection. These packages were published to do harm, so they carry no CVE, CVSS or EPSS score. They are matched by package name and version like any other advisory. 93% of them are npm packages. The collection starts in 2022.
malicious-package reports since 2022
of them on npm
from one spam campaign, tea.xyz, in 2025
legitimate packages taken over, at least
Show as table
| Year | tea.xyz | Other | Taken over (within other) | Total |
|---|---|---|---|---|
| 2022 | 0 | 7,445 | 0 | 7,445 |
| 2023 | 0 | 8,775 | 0 | 8,775 |
| 2024 | 0 | 12,491 | 0 | 12,491 |
| 2025 | 140,728 | 51,987 | 308 | 192,715 |
| 2026 | 0 | 19,821 | 850 | 19,821 |
Most of 2025's 192,715 reports trace back to tea.xyz token farming. Its 140,728 packages run scripts that publish copies of themselves under random names, which raises their authors' standing for tea protocol token rewards. Most of them were reported within a few days in November. Without them 2025 still has 51,987 reports, about four times 2024, including a single batch of about 34,000 packages reported on 14 August with names like raid-shadow-legends-codes and google-play-card-balance. 2026 has 19,821 so far.
| Ecosystem | 2022 | 2023 | 2024 | 2025 | 2026 |
|---|---|---|---|---|---|
| npm | 7,424 | 2,291 | 8,317 | 50,579 | 14,723 |
| PyPI | 20 | 6,467 | 2,645 | 1,246 | 1,656 |
| RubyGems | 0 | 16 | 791 | 129 | 3,385 |
| NuGet | 0 | 0 | 738 | 22 | 22 |
| crates.io | 1 | 1 | 0 | 1 | 22 |
| Go | 0 | 0 | 0 | 8 | 12 |
A much smaller group of reports covers legitimate, widely used packages whose maintainers' accounts were taken over and given malicious new versions. The report text names at least 1,158 of them, 308 in 2025, among them ansi-styles, and 850 in 2026, most of them attributed to the Shai-Hulud worm. In one wave a single stolen npm account published 631 malicious versions across 314 packages in 22 minutes, each one stealing cloud keys, GitHub tokens and npm tokens from the machine that installed it.
| Campaign | Reports | Years | Ecosystems |
|---|---|---|---|
| tea.xyz token farming | 140,728 | 2025 | npm |
| EsqueleSquad spyware and infostealers | 5,425 | 2023 | PyPI, npm |
| Malicious browser extension installer | 900 | 2023 | PyPI |
| Shai-Hulud worm (maintainer accounts taken over) | 812 | 2025-2026 | npm, PyPI |
| Dependency confusion | 313 | 2024-2026 | npm, PyPI |
| Lazarus Group | 53 | 2023 | npm |
Methodology
How were these numbers made?
- Data. The ShieldedStack advisory database on 18 November 2026: advisories from GitHub, PyPA, the Go vulnerability database, RustSec, the Erlang Ecosystem Foundation, Drupal and the OpenSSF Malicious Packages collection, joined with NVD's CVE records, CISA's KEV catalogue, and the Linux distributions' own advisories for reach.
- Scope. A CVE counts when at least one live advisory links it to a package in npm, PyPI, Maven, Go, NuGet, crates.io, Packagist, RubyGems, Hex, Swift, Pub or GitHub Actions. Operating system and container advisories are out of scope. Malicious-package reports are not CVEs and have their own section.
- Year. The year NVD published the CVE, which can differ from the year in its id. CVE-2020-17519 was published in 2021 and counts there.
- Excluded. 78 CVEs NVD has rejected, and CVEs whose only package advisories have been withdrawn. Vulnerabilities without a CVE are counted separately, by the advisory's published date, grouping advisories that name each other.
- Sources per ecosystem. npm, Maven, NuGet and RubyGems advisories come from GitHub's reviewed advisory database. PyPI, Go, crates.io, Hex and Packagist also have a source of their own. A CVE for a package none of these sources has reviewed is not in the count.
- CVSS. The CVE's own score: the CNA's vectors first, then NVD's, then CISA's, taking the newest CVSS version each scored.
- Top 10 ranking. Critical CVEs only, ordered by KEV listing, then the number of ecosystems and distributions with an advisory for the CVE, then the number of packages, then CVSS. KEV began in late 2021 and older CVEs were added later, so a listing means exploited at some point, not necessarily in that year. EPSS is not used because only today's score is available.
- Malicious packages. Counted by the date each report was published, without withdrawn reports. "tea.xyz" means the report's text names that campaign; "taken over" means the text says the package or its maintainer's account was compromised. Many reports use generic wording, so both are lower bounds.
- Categories. NVD's CWE ids grouped into families. "Unclassified" means NVD lists no CWE or only NVD-CWE-noinfo.
Category mapping
- Cross-site scripting
- CWE-79, CWE-80
- Injection (SQL, command, code, template)
- CWE-74, CWE-77, CWE-78, CWE-88, CWE-89, CWE-94, CWE-95, CWE-917, CWE-1336, CWE-943, CWE-90, CWE-91
- Path traversal & file handling
- CWE-22, CWE-23, CWE-24, CWE-29, CWE-35, CWE-36, CWE-59, CWE-61, CWE-73, CWE-434, CWE-552
- Broken access control & auth
- CWE-284, CWE-285, CWE-862, CWE-863, CWE-287, CWE-306, CWE-639, CWE-269, CWE-266, CWE-288, CWE-290, CWE-307, CWE-613, CWE-620, CWE-640, CWE-522, CWE-1390, CWE-345, CWE-346, CWE-924, CWE-425, CWE-280, CWE-732, CWE-276, CWE-384, CWE-798, CWE-294, CWE-915, CWE-1188, CWE-521, CWE-565, CWE-942, CWE-1385
- SSRF
- CWE-918
- Unsafe deserialization
- CWE-502
- Resource exhaustion / DoS
- CWE-400, CWE-770, CWE-1333, CWE-674, CWE-835, CWE-789, CWE-834, CWE-405, CWE-407, CWE-409, CWE-1050, CWE-617, CWE-369, CWE-404, CWE-248, CWE-772, CWE-1325
- Memory safety
- CWE-119, CWE-120, CWE-121, CWE-122, CWE-125, CWE-787, CWE-416, CWE-415, CWE-476, CWE-190, CWE-191, CWE-131, CWE-704, CWE-908, CWE-457, CWE-401, CWE-824, CWE-843, CWE-682
- Information exposure
- CWE-200, CWE-201, CWE-209, CWE-532, CWE-538, CWE-359, CWE-212, CWE-497, CWE-312, CWE-313, CWE-668
- CSRF
- CWE-352
- Prototype pollution
- CWE-1321
- Cryptography & TLS
- CWE-295, CWE-297, CWE-310, CWE-311, CWE-319, CWE-326, CWE-327, CWE-328, CWE-330, CWE-331, CWE-335, CWE-338, CWE-347, CWE-354, CWE-757, CWE-916, CWE-208, CWE-203, CWE-385
- XXE
- CWE-611, CWE-776
- Open redirect
- CWE-601
- Request smuggling & HTTP parsing
- CWE-444, CWE-113, CWE-93, CWE-644
- Race conditions
- CWE-362, CWE-367, CWE-364, CWE-366
- Improper input validation
- CWE-20, CWE-1284, CWE-1287, CWE-129, CWE-116, CWE-117, CWE-150, CWE-838, CWE-172, CWE-180, CWE-184