VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

cloudinary: vulnerability history, versions and safety

cloudinary is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 114 releases, first recorded in Nov 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded H1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 10 Nov 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all cloudinary vulnerabilities

Vulert verdict on cloudinary 2.11.0 i

Updated on 23 Oct 2026

Good news: 2.11.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 78/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 2.11.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 10 Nov 2025 i
  • Highest CVSS 8.6 i
  • With no published fix 0 i
  • Depended on by 316 packages i
  • Stars 670 i
  • OpenSSF scorecard 4/10 i
  • Last release 1 month ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 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 cloudinary, 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.11.0 27 Aug 2026 none MIT — Details →
2.10.1 19 Aug 2026 none MIT — Details →
2.10.0 25 Apr 2026 none MIT — Details →
2.9.0 16 Jan 2026 none MIT — Details →
2.8.0 20 Oct 2025 none MIT — Details →
2.7.0 18 Jun 2025 none MIT — Details →
2.6.1 05 May 2025 H1 MIT Yes Details →
2.6.1-rc.1 05 May 2025 H1 MIT Yes Details →
2.6.0 11 Mar 2025 H1 MIT Yes Details →
2.5.1 08 Oct 2024 H1 MIT Yes Details →
2.5.0 15 Sep 2024 H1 MIT Yes Details →
2.4.0 30 Jul 2024 H1 MIT Yes Details →
2.3.1 25 Jul 2024 H1 MIT Yes Details →
2.3.0 16 Jul 2024 H1 MIT Yes Details →
2.2.0 22 Apr 2024 H1 MIT Yes Details →
2.1.0 29 Mar 2024 H1 MIT Yes Details →
2.0.3 05 Mar 2024 H1 MIT Yes Details →
2.0.2 01 Mar 2024 H1 MIT Yes Details →
2.0.1 07 Feb 2024 H1 MIT Yes Details →
2.0.0 29 Jan 2024 H1 MIT Yes Details →
1.41.3 18 Jan 2024 H1 MIT Yes Details →
2.0.0-rc.1 18 Jan 2024 H1 MIT Yes Details →
1.41.2 08 Jan 2024 H1 MIT Yes Details →
2.0.0-rc 08 Jan 2024 H1 MIT Yes Details →
1.41.1 18 Dec 2023 H1 MIT Yes Details →
1.41.0 26 Sep 2023 H1 MIT Yes Details →
1.40.0 31 Jul 2023 H1 MIT Yes Details →
1.39.0 24 Jul 2023 H1 MIT Yes Details →
1.38.0 20 Jul 2023 H1 MIT Yes Details →
1.37.3 26 Jun 2023 H1 MIT Yes Details →
1.37.2 19 Jun 2023 H1 MIT Yes Details →
1.37.1 09 Jun 2023 H1 MIT Yes Details →
1.37.0 16 May 2023 H1 MIT Yes Details →
1.36.4 02 May 2023 H1 MIT Yes Details →
1.36.3 02 May 2023 H1 MIT Yes Details →
1.36.2 24 Apr 2023 H1 MIT Yes Details →
1.36.1 13 Apr 2023 H1 MIT Yes Details →
1.36.0 13 Apr 2023 H1 MIT Yes Details →
1.35.0 03 Mar 2023 H1 MIT Yes Details →
1.34.0 13 Feb 2023 H1 MIT Yes Details →
1.33.0 15 Dec 2022 H1 MIT Yes Details →
1.32.0 14 Sep 2022 H1 MIT Yes Details →
1.31.0 28 Aug 2022 H1 MIT Yes Details →
1.30.1 21 Jul 2022 H1 MIT Yes Details →
1.30.0 15 May 2022 H1 MIT Yes Details →
1.29.1 17 Apr 2022 H1 MIT Yes Details →
1.29.0 24 Mar 2022 H1 MIT Yes Details →
1.28.1 06 Jan 2022 H1 MIT Yes Details →
1.28.0 02 Jan 2022 H1 MIT Yes Details →
1.27.1 11 Oct 2021 H1 MIT Yes Details →
1.27.0 12 Sep 2021 H1 MIT Yes Details →
1.26.3 01 Aug 2021 H1 MIT Yes Details →
1.26.2 04 Jul 2021 H1 MIT Yes Details →
1.26.1 22 Jun 2021 H1 MIT Yes Details →
1.26.0 06 Jun 2021 H1 MIT Yes Details →
1.25.2 30 May 2021 H1 MIT Yes Details →
1.25.1 22 Mar 2021 H1 MIT Yes Details →
1.25.0 22 Feb 2021 H1 MIT Yes Details →
1.24.0 31 Jan 2021 H1 MIT Yes Details →
1.23.0 26 Aug 2020 H1 MIT Yes Details →
1.22.0 08 Jun 2020 H1 MIT Yes Details →
1.21.0 29 Mar 2020 H1 MIT Yes Details →
1.20.0 11 Mar 2020 H1 MIT Yes Details →
1.19.0 20 Jan 2020 H1 MIT Yes Details →
1.18.1 11 Dec 2019 H1 MIT Yes Details →
1.18.0 09 Dec 2019 H1 MIT Yes Details →
1.17.0 11 Nov 2019 H1 MIT Yes Details →
1.16.0 15 Oct 2019 H1 MIT Yes Details →
1.15.0 08 Sep 2019 H1 MIT Yes Details →
1.14.0 26 Mar 2019 H1 MIT Yes Details →
1.13.2 14 Nov 2018 H1 MIT Yes Details →
1.13.1 13 Nov 2018 H1 MIT Yes Details →
1.13.0 12 Nov 2018 H1 MIT Yes Details →
1.12.0 08 Nov 2018 H1 MIT Yes Details →
1.11.0 19 Mar 2018 H1 MIT Yes Details →
1.10.0 13 Feb 2018 H1 MIT Yes Details →
1.9.1 24 Oct 2017 H1 MIT Yes Details →
1.9.0 30 Apr 2017 H1 MIT Yes Details →
1.8.0 09 Mar 2017 H1 MIT Yes Details →
1.7.1 22 Feb 2017 H1 MIT Yes Details →
1.7.0 08 Feb 2017 H1 MIT Yes Details →
1.6.0 30 Jan 2017 H1 MIT Yes Details →
1.5.0 29 Dec 2016 H1 MIT Yes Details →
1.4.6 25 Nov 2016 H1 MIT Yes Details →
1.4.5 25 Nov 2016 H1 MIT Yes Details →
1.4.4 27 Oct 2016 H1 MIT Yes Details →
1.4.3 21 Sep 2016 H1 MIT Yes Details →
1.4.2 15 Sep 2016 H1 MIT Yes Details →
1.4.1 22 Jun 2016 H1 MIT Yes Details →
1.4.0 22 Jun 2016 H1 MIT Yes Details →
1.3.1 03 Apr 2016 H1 MIT Yes Details →
1.3.0 08 Jan 2016 H1 MIT Yes Details →
1.2.6 19 Nov 2015 H1 MIT Yes Details →
1.2.5 14 Oct 2015 H1 MIT Yes Details →
1.2.4 09 Aug 2015 H1 MIT Yes Details →
1.2.3 09 Aug 2015 H1 MIT Yes Details →
1.2.2 20 Jul 2015 H1 MIT Yes Details →
1.2.1 16 Apr 2015 H1 MIT Yes Details →
1.2.0 07 Apr 2015 H1 MIT Yes Details →
1.1.2 26 Feb 2015 H1 MIT Yes Details →
1.1.1 22 Dec 2014 H1 — Yes Details →
1.1.0 02 Dec 2014 H1 — Yes Details →
1.0.13 09 Nov 2014 H1 — Yes Details →
1.0.12 28 Aug 2014 H1 — Yes Details →
1.0.11 17 Jul 2014 H1 — Yes Details →
1.0.10 07 Jul 2014 H1 — Yes Details →
1.0.9 29 Apr 2014 H1 — Yes Details →
1.0.8 27 Feb 2014 H1 — Yes Details →
1.0.7 09 Jan 2014 H1 — Yes Details →
1.0.6 04 Nov 2013 H1 — Yes Details →
1.0.5 07 Aug 2013 H1 — Yes Details →
1.0.4 30 Jul 2013 H1 — Yes Details →
1.0.3 01 Jul 2013 H1 — Yes Details →
1.0.2 14 Mar 2013 H1 — Yes Details →
1.0.1 15 Jan 2013 H1 — Yes Details →
0.2.7 07 Dec 2012 H1 — Yes Details →
0.2.6 28 Oct 2012 H1 — Yes Details →
0.2.5 08 Oct 2012 H1 — Yes Details →
0.2.4 02 Oct 2012 H1 — Yes Details →
0.2.3 27 Jul 2012 H1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for cloudinary

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-12613: Cloudinary Node SDK Arbitrary Argument Injection Vulnerability 8.6 high 2.7.0 10 Nov 2025

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 cloudinary

Is cloudinary safe to use?

Vulert records 1 vulnerabilities for cloudinary in npm: 0 critical, 1 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is cloudinary's Vulert package health score?

Vulert scores cloudinary 78/100, which reads as in good shape. 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 cloudinary affected?

No. 2.11.0, 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.

Which version of cloudinary should I use?

2.11.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does cloudinary have?

1 vulnerability is recorded for cloudinary in the npm ecosystem: 0 critical, 1 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 cloudinary vulnerabilities disclosed?

1 vulnerability was recorded for cloudinary in the last 12 months, and the oldest entry in this database dates to 10 Nov 2025. 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 cloudinary 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 cloudinary for upcoming vulnerabilities?

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