VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@vercel/blob: vulnerability history, versions and safety

@vercel/blob is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the npm ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @vercel/blob vulnerabilities

Vulert verdict on @vercel/blob 2.8.2 i

Updated on 23 Oct 2026

Good news: 2.8.2, the version you would install today, has no known vulnerabilities.

Package health score 91/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

What to do: Stay on 2.8.2 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.8.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2.8.2 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 337 packages i
  • Stars 599 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for @vercel/blob, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.9.0-0cc97b0-20261014190917 14 Oct 2026 none Apache-2.0 — Details →
2.9.0-2c74279-20261014104540 14 Oct 2026 none Apache-2.0 — Details →
2.9.0-b041c57-20261014103439 14 Oct 2026 none Apache-2.0 — Details →
2.8.2 14 Oct 2026 none Apache-2.0 — Details →
2.8.1 06 Oct 2026 none Apache-2.0 — Details →
2.8.0 10 Aug 2026 none Apache-2.0 — Details →
2.8.0-76c89fb-20260810184411 10 Aug 2026 none Apache-2.0 — Details →
2.7.0 06 Aug 2026 none Apache-2.0 — Details →
2.7.0-ad5a134-20260805193409 05 Aug 2026 none Apache-2.0 — Details →
2.6.1 08 Jul 2026 none Apache-2.0 — Details →
2.6.0 07 Jul 2026 none Apache-2.0 — Details →
2.5.0 25 Jun 2026 none Apache-2.0 — Details →
2.4.2-4f3596e-20260625125357 25 Jun 2026 none Apache-2.0 — Details →
2.4.1 18 Jun 2026 none Apache-2.0 — Details →
2.4.1-b7027de-20260616193056 16 Jun 2026 none Apache-2.0 — Details →
2.4.0 18 May 2026 none Apache-2.0 — Details →
2.3.4-c199a29-20260515173441 15 May 2026 none Apache-2.0 — Details →
2.3.4-8b17a14-20260507180422 07 May 2026 none Apache-2.0 — Details →
2.3.4-9a05ef7-20260507175557 07 May 2026 none Apache-2.0 — Details →
2.3.4-a5ceef9-20260507043656 07 May 2026 none Apache-2.0 — Details →
2.3.4-52fd7bc-20260507000318 07 May 2026 none Apache-2.0 — Details →
2.3.4-128dc33-20260506234516 06 May 2026 none Apache-2.0 — Details →
2.3.4-916b4c4-20260506230516 06 May 2026 none Apache-2.0 — Details →
2.3.4-6010219-20260506230045 06 May 2026 none Apache-2.0 — Details →
2.3.4-05eb596-20260506224745 06 May 2026 none Apache-2.0 — Details →
2.3.4-9a55b7d-20260506224323 06 May 2026 none Apache-2.0 — Details →
2.3.4-4cd4da4-20260506223235 06 May 2026 none Apache-2.0 — Details →
2.3.4-a659982-20260506222004 06 May 2026 none Apache-2.0 — Details →
2.3.4-ac3f656-20260506220025 06 May 2026 none Apache-2.0 — Details →
2.3.4-1ce589e-20260506200814 06 May 2026 none Apache-2.0 — Details →
2.3.4-a65182b-20260506163949 06 May 2026 none Apache-2.0 — Details →
2.3.4-83f2da4-20260505202344 05 May 2026 none Apache-2.0 — Details →
2.3.4-40fd456-20260505201635 05 May 2026 none Apache-2.0 — Details →
2.3.4-abeb564-20260505173950 05 May 2026 none Apache-2.0 — Details →
2.3.4-1a02707-20260504180753 04 May 2026 none Apache-2.0 — Details →
2.3.4-dfec20e-20260430222954 30 Apr 2026 none Apache-2.0 — Details →
2.3.4-5d06fa0-20260428215217 28 Apr 2026 none Apache-2.0 — Details →
2.3.4-179061a-20260428210614 28 Apr 2026 none Apache-2.0 — Details →
2.3.3 02 Apr 2026 none Apache-2.0 — Details →
2.3.3-f8b7d06-20260402140007 02 Apr 2026 none Apache-2.0 — Details →
2.3.3-f13c642-20260402132839 02 Apr 2026 none Apache-2.0 — Details →
2.3.2 27 Mar 2026 none Apache-2.0 — Details →
2.3.1 04 Mar 2026 none Apache-2.0 — Details →
2.3.0 19 Feb 2026 none Apache-2.0 — Details →
2.3.0-cc8f7be-20260217140255 17 Feb 2026 none Apache-2.0 — Details →
2.3.0-9e312ca-20260217131947 17 Feb 2026 none Apache-2.0 — Details →
2.3.0-45afd02-20260217101240 17 Feb 2026 none Apache-2.0 — Details →
2.3.0-512846a-20260206231709 06 Feb 2026 none Apache-2.0 — Details →
2.2.0 06 Feb 2026 none Apache-2.0 — Details →
2.2.0-f6bb7b4-20260204165325 04 Feb 2026 none Apache-2.0 — Details →
2.1.0 04 Feb 2026 none Apache-2.0 — Details →
2.1.0-454414f-20260204161813 04 Feb 2026 none Apache-2.0 — Details →
2.1.0-73e660a-20260202164138 02 Feb 2026 none Apache-2.0 — Details →
2.1.0-f8529bc-20260129224154 29 Jan 2026 none Apache-2.0 — Details →
2.1.0-4adc7b7-20260129165900 29 Jan 2026 none Apache-2.0 — Details →
2.1.0-062a059-20260128141057 28 Jan 2026 none Apache-2.0 — Details →
2.1.0-f0898fb-20260127125323 27 Jan 2026 none Apache-2.0 — Details →
2.1.0-704ff70-20260126150218 26 Jan 2026 none Apache-2.0 — Details →
2.1.0-704ff70-20260123180156 23 Jan 2026 none Apache-2.0 — Details →
2.0.1 23 Jan 2026 none Apache-2.0 — Details →
2.1.0-06d6754-20260122183144 22 Jan 2026 none Apache-2.0 — Details →
2.1.0-39df1d8-20260121161119 21 Jan 2026 none Apache-2.0 — Details →
2.1.0-371428d-20260119152220 19 Jan 2026 none Apache-2.0 — Details →
2.0.0 16 Sep 2025 none Apache-2.0 — Details →
2.0.0-831c3252-20250912073217 12 Sep 2025 none Apache-2.0 — Details →
2.0.0-4d25be25-20250912070808 12 Sep 2025 none Apache-2.0 — Details →
1.1.1 23 May 2025 none Apache-2.0 — Details →
1.1.0 22 May 2025 none Apache-2.0 — Details →
1.1.0-3c8c8d5f-20250522093509 22 May 2025 none Apache-2.0 — Details →
1.0.2 19 May 2025 none Apache-2.0 — Details →
1.0.1 02 May 2025 none Apache-2.0 — Details →
1.0.0 10 Apr 2025 none Apache-2.0 — Details →
1.0.0-907570c7-20250410144756 10 Apr 2025 none Apache-2.0 — Details →
0.27.3 13 Mar 2025 none Apache-2.0 — Details →
0.27.2 27 Feb 2025 none Apache-2.0 — Details →
0.27.2-7f767887-20250226154637 26 Feb 2025 none Apache-2.0 — Details →
0.27.1 17 Jan 2025 none Apache-2.0 — Details →
0.27.1-0372ed96-20250113161609 13 Jan 2025 none Apache-2.0 — Details →
0.27.0 04 Dec 2024 none Apache-2.0 — Details →
0.26.0 06 Nov 2024 none Apache-2.0 — Details →
0.26.0-682d4ba8-20241106132652 06 Nov 2024 none Apache-2.0 — Details →
0.26.0-682d4ba8-20241106093032 06 Nov 2024 none Apache-2.0 — Details →
0.26.0-aabdf547-20241106084915 06 Nov 2024 none Apache-2.0 — Details →
0.26.0-aabdf547-20241106081612 06 Nov 2024 none Apache-2.0 — Details →
0.26.0-aabdf547-20241105160622 05 Nov 2024 none Apache-2.0 — Details →
0.26.0-5bff1ec3-20241105160133 05 Nov 2024 none Apache-2.0 — Details →
0.26.0-a6fd11fa-20241105153621 05 Nov 2024 none Apache-2.0 — Details →
0.26.0-a0c75211-20241025223154 25 Oct 2024 none Apache-2.0 — Details →
0.25.1 14 Oct 2024 none Apache-2.0 — Details →
0.25.0 08 Oct 2024 none Apache-2.0 — Details →
0.24.1 03 Oct 2024 none Apache-2.0 — Details →
0.24.0 16 Sep 2024 none Apache-2.0 — Details →
0.23.4 01 Jul 2024 none Apache-2.0 — Details →
0.23.3 21 May 2024 none Apache-2.0 — Details →
0.23.3-e14181a4-20240517133706 17 May 2024 none Apache-2.0 — Details →
0.23.2 18 Apr 2024 none Apache-2.0 — Details →
0.23.1 18 Apr 2024 none Apache-2.0 — Details →
0.23.0 17 Apr 2024 none Apache-2.0 — Details →
0.23.0-f6147d74-20240411135804 11 Apr 2024 none Apache-2.0 — Details →
0.23.0-a6b0ece4-20240411134808 11 Apr 2024 none Apache-2.0 — Details →
0.22.3 08 Apr 2024 none — — Details →
0.22.2 04 Apr 2024 none — — Details →
0.22.1 21 Feb 2024 none — — Details →
0.22.1-0cb7edd4-20240221003206 21 Feb 2024 none — — Details →
0.22.0 12 Feb 2024 none — — Details →
0.21.0 06 Feb 2024 none — — Details →
0.20.0 30 Jan 2024 none — — Details →
0.19.0 18 Jan 2024 none — — Details →
0.19.0-8de77fbc-20240116145546 16 Jan 2024 none — — Details →
0.18.0 15 Jan 2024 none — — Details →
0.17.1 15 Jan 2024 none — — Details →
0.17.0 12 Jan 2024 none — — Details →
0.16.2 12 Jan 2024 none — — Details →
0.17.0-c2239f49-20240111125313 11 Jan 2024 none — — Details →
0.17.0-c2239f49-20231218111237 18 Dec 2023 none — — Details →
0.16.0-99c35286-20231214174115 14 Dec 2023 none — — Details →
0.16.0-a06e5b22-20231214173003 14 Dec 2023 none — — Details →
0.16.1 13 Dec 2023 none — — Details →
0.16.1-2e8490f0-20231213124417 13 Dec 2023 none — — Details →
0.16.1-14fade3a-20231208224408 08 Dec 2023 none — — Details →

The newest 120 of 184 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for @vercel/blob

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About @vercel/blob

Is @vercel/blob safe to use?

Vulert has no vulnerabilities on record for @vercel/blob in npm at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is @vercel/blob's Vulert package health score?

Vulert scores @vercel/blob 91/100, which reads as healthy. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of @vercel/blob affected?

No. 2.8.2, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does @vercel/blob have?

0 vulnerabilities are recorded for @vercel/blob in the npm ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new @vercel/blob vulnerabilities disclosed?

0 vulnerabilities were recorded for @vercel/blob in the last 12 months. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of @vercel/blob are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor @vercel/blob for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @vercel/blob version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.