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.
33,039

CVEs affecting open source packages, 2017 to 18 Nov 2026

Source: ShieldedStack advisory database

12,154

package CVEs published in 2026 so far

Source: ShieldedStack advisory database

3.5x

2026 to date against all of 2025

Source: ShieldedStack advisory database

241,252

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.

CVEs published per year2026 counts up to 18 November
03,7507,50011,25015,00081820171,61520181,59320191,94520202,27620213,23520223,06220232,88720243,454202512,1542026
Show as table
YearCVEsOn KEV
20178188
20181,61510
20191,59310
20201,94518
20212,27614
20223,2359
20233,06210
20242,8875
20253,45420
202612,15417

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.

CVEs published per monthNovember 2026 is partial
03757501,1251,5002017201820192020202120222023202420252026March 2026
Show as table
MonthCVEs
2017-0154
2017-0234
2017-0364
2017-0473
2017-0568
2017-0635
2017-0767
2017-0893
2017-0983
2017-10108
2017-1194
2017-1245
2018-01149
2018-0280
2018-03109
2018-0476
2018-05168
2018-06471
2018-07137
2018-08106
2018-0981
2018-1073
2018-1170
2018-1295
2019-0198
2019-0274
2019-0395
2019-04205
2019-0587
2019-0672
2019-07140
2019-08221
2019-09154
2019-10139
2019-11192
2019-12116
2020-01167
2020-02127
2020-03210
2020-04119
2020-05125
2020-06227
2020-07164
2020-0889
2020-09208
2020-10119
2020-11155
2020-12235
2021-01182
2021-02183
2021-03207
2021-04168
2021-05267
2021-06161
2021-07100
2021-08308
2021-09160
2021-10129
2021-11207
2021-12204
2022-01238
2022-02318
2022-03327
2022-04182
2022-05244
2022-06305
2022-07212
2022-08220
2022-09362
2022-10206
2022-11285
2022-12336
2023-01255
2023-02240
2023-03324
2023-04302
2023-05239
2023-06243
2023-07234
2023-08218
2023-09254
2023-10248
2023-11238
2023-12267
2024-01247
2024-02283
2024-03272
2024-04246
2024-05255
2024-06216
2024-07245
2024-08208
2024-09211
2024-10286
2024-11247
2024-12171
2025-01268
2025-02184
2025-03402
2025-04272
2025-05242
2025-06254
2025-07261
2025-08295
2025-09344
2025-10363
2025-11234
2025-12335
2026-01467
2026-02668
2026-031,355
2026-041,267
2026-051,421
2026-061,361
2026-071,348
2026-081,365
2026-091,186
2026-101,333
2026-11383

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.

CVEs per ecosystem and yearShading is relative to each ecosystem's busiest year; a CVE in several ecosystems counts in each
Ecosystem20172018201920202021202220232024202520262026 vs 2025
npm565491503654184643623945423,3126.1x
Maven2904675925524979369175296711,0231.5x
PyPI1581421822494795565156787292,6063.6x
Packagist (PHP)1922323973174206716495506431,7012.6x
Go2848812431744424675336492,1933.4x
crates.io (Rust)11431062227066831184734.0x
NuGet50122987034556192914034.4x
RubyGems5784766869806989582293.9x
Hex (Erlang/Elixir)43521275932035.6x
Swift00000041610.2x
GitHub Actions0000000008new

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.

2026 vulnerabilities without a CVE, per ecosystemAdvisories from several sources for one flaw count once
EcosystemWith a CVEWithoutShare without
crates.io (Rust)47340946%
Go2,1931506%
PyPI2,6061515%
npm3,3122166%
NuGet403256%
RubyGems229125%
Packagist (PHP)1,701533%
Maven1,023212%
Hex (Erlang/Elixir)32000%

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.

Share of each year's CVEs, by categoryA CVE with weaknesses in two categories counts in both
Access control & authCross-site scriptingInjectionResource exhaustion (DoS)Path traversal & filesMemory safety
0%10%20%30%2017201820192020202120222023202420252026
Show as table
Category2017201820192020202120222023202420252026
Access control & auth12.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 scripting18.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)
Injection7.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 & files5.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 safety7.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.

Severity mix per yearFrom the CVE's own CVSS score, newest CVSS version
CriticalHighMediumLow
0%25%50%75%100%2017201820192020202120222023202420252026
Show as table
YearCriticalHighMediumLow
201714434631810
201819183457218
201923660572824
202034966987354
2021360811962143
20224781,1151,527113
20234671,0361,382175
20243679961,324195
20253611,0521,687351
20261,3444,8475,002931

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
EcosystemPackageFixed in
Mavenorg.apache.tomcat.embed:tomcat-embed-core9.0.99, 10.1.35, 11.0.3
Mavenorg.apache.tomcat:tomcat-catalina9.0.99, 10.1.35, 11.0.3
CVE-2025-24813 in the ShieldedStack advisory database →
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
EcosystemPackageFixed in
Packagistroundcube/roundcubemail1.5.10, 1.6.11
CVE-2025-49113 in the ShieldedStack advisory database →
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
EcosystemPackageFixed in
PyPIray2.52.0
CVE-2025-62593 in the ShieldedStack advisory database →
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
EcosystemPackageFixed in
Gogithub.com/wazuh/wazuh4.9.1, 4.9.1+incompatible
CVE-2025-24016 in the ShieldedStack advisory database →
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
EcosystemPackageFixed in
npmreact-server-dom-parcel19.0.1, 19.1.2, 19.2.1
npmreact-server-dom-turbopack19.0.1, 19.1.2, 19.2.1
npmreact-server-dom-webpack19.0.1, 19.1.2, 19.2.1
CVE-2025-55182 in the ShieldedStack advisory database →
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
EcosystemPackageFixed in
npm@react-native-community/cli18.0.1, 19.1.2, 20.0.0
npm@react-native-community/cli-server-api18.0.1, 19.1.2, 20.0.0
CVE-2025-11953 in the ShieldedStack advisory database →
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
EcosystemPackageFixed in
PyPIlangflow1.3.0
PyPIlangflow-base0.3.0
CVE-2025-3248 in the ShieldedStack advisory database →
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
EcosystemPackageFixed in
Packagistmagento/community-editionNo fixed version listed
Packagistmagento/project-community-editionNo fixed version listed
CVE-2025-54236 in the ShieldedStack advisory database →
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
EcosystemPackageFixed in
Packagistcraftcms/cms3.9.15, 4.14.15, 5.6.17
CVE-2025-32432 in the ShieldedStack advisory database →
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
EcosystemPackageFixed in
npmn8n1.120.4, 1.121.1
CVE-2025-68613 in the ShieldedStack advisory database →

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.

241,252

malicious-package reports since 2022

93%

of them on npm

140,728

from one spam campaign, tea.xyz, in 2025

1,158

legitimate packages taken over, at least

Malicious-package reports per year2026 counts up to 18 November
All other reportstea.xyz token farming
050,000100,000150,000200,0007,44520228,775202312,4912024192,715202519,8212026
Show as table
Yeartea.xyzOtherTaken over (within other)Total
202207,44507,445
202308,77508,775
2024012,491012,491
2025140,72851,987308192,715
2026019,82185019,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.

Reports per ecosystem and year, without tea.xyzShading is relative to each ecosystem's busiest year
Ecosystem20222023202420252026
npm7,4242,2918,31750,57914,723
PyPI206,4672,6451,2461,656
RubyGems0167911293,385
NuGet007382222
crates.io110122
Go000812

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.

Campaigns named in the reportsOnly reports whose text names the campaign
CampaignReportsYearsEcosystems
tea.xyz token farming140,7282025npm
EsqueleSquad spyware and infostealers5,4252023PyPI, npm
Malicious browser extension installer9002023PyPI
Shai-Hulud worm (maintainer accounts taken over)8122025-2026npm, PyPI
Dependency confusion3132024-2026npm, PyPI
Lazarus Group532023npm
Who reported themA report can credit several reporters
All other reportstea.xyz token farming
Amazon Inspector154,433
GitHub (malware advisories)29,979
ReversingLabs18,142
Checkmarx6,516
OpenSSF Package Analysis5,935
kam193 (independent researcher)3,304
Google Open Source Security1,981
Oracle (Macaron)32
No reporter listed40,150
Look up any package, CVE or advisory in the ShieldedStack advisory database. For the attacks behind these numbers, see the State of the Software Supply Chain 2026 and the top 10 supply chain attacks.

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