CVE-2025-12613: Cloudinary Cloudinary Node SDK Is Vulnerable Vulnerability

HIGH
Advisory Identifier: GHSA-g4mf-96x5-5m2c
CVSS 8.6
CWE-88
Published
Advisory Summary

CVE-2025-12613 is a HIGH (CVSS 8.6) cloudinary node sdk is vulnerable vulnerability (CWE-88: Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')) affecting Cloudinary libraries in the npm ecosystem. The issue involves cloudinary node sdk is vulnerable to arbitrary argument injection through parameters that include an ampersand. Remediation is available by upgrading affected packages to version 2.7.0.

CVE-2025-12613 at a Glance

CVE Identifier CVE-2025-12613
GHSA Identifier GHSA-g4mf-96x5-5m2c
Severity HIGH
CVSS v3.1 Base Score 8.6
CWE Classification CWE-88: Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')
Affected Product Cloudinary
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 8.6

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity High (I:H)
Availability Low (A:L)

How to Fix CVE-2025-12613

To remediate this vulnerability, upgrade all affected Cloudinary dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

cloudinary fixed: 2.7.0
npm install cloudinary@2.7.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls cloudinary

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2025-12613, inspect your project dependencies using npm:

npm ls cloudinary

Analyze the terminal output to locate any version of Cloudinary in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.7.0), your application is affected.

Note: The npm ls cloudinary command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-88: Improper Neutralization of Argument Delimiters in a Command ('Argument Injection'), where the product constructs a string for a command to be executed by a separate component in another control sphere, but it does not properly delimit the intended arguments, options, or switches within that command string. In Cloudinary, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

Versions of the package cloudinary before 2.7.0 are vulnerable to Arbitrary Argument Injection due to improper parsing of parameter values containing an ampersand. An attacker can inject additional, unintended parameters. This could lead to a variety of malicious outcomes, such as bypassing security checks, altering data, or manipulating the application's behavior. **Note:** Following our established security policy, we attempted to contact the maintainer regarding this vulnerability, but haven't received a response.

CVE-2025-12613 Affected Cloudinary Versions

1 component(s)
Fixed Versions:
2.7.0
Product / Package Ecosystem Affected Versions Fixed Version
cloudinary
npm
< 2.7.0
2.7.0

References

Frequently Asked Questions

What is CVE-2025-12613?
CVE-2025-12613 is a security vulnerability in Cloudinary involving Cloudinary Node SDK is vulnerable to Arbitrary Argument Injection through parameters that include an ampersand under CWE-88: Improper Neutralization of Argument Delimiters in a Command ('Argument Injection').
Which Cloudinary versions are affected?
Affected versions include releases prior to 2.7.0 across affected packages: cloudinary.
What version fixes CVE-2025-12613?
Upgrading to 2.7.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is cloudinary affected?
Yes, cloudinary is affected in releases prior to 2.7.0. Upgrade your dependency to 2.7.0 or later.
What is the CVSS score of CVE-2025-12613?
CVE-2025-12613 has a CVSS v3.1 base score of 8.6 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L.
What CWE is associated with CVE-2025-12613?
CVE-2025-12613 is classified under CWE-88: Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') (The product constructs a string for a command to be executed by a separate component in another control sphere, but it does not properly delimit the intended arguments, options, or switches within that command string.).
How can I check npm dependencies for CVE-2025-12613?
Run the dependency tree command: 'npm ls cloudinary'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-g4mf-96x5-5m2c",
  "modified" : "2025-11-12T23:41:30Z",
  "published" : "2025-11-10T06:30:26Z",
  "aliases" : [ "CVE-2025-12613" ],
  "summary" : "Cloudinary Node SDK is vulnerable to Arbitrary Argument Injection through parameters that include an ampersand",
  "details" : "Versions of the package cloudinary before 2.7.0 are vulnerable to Arbitrary Argument Injection due to improper parsing of parameter values containing an ampersand. An attacker can inject additional, unintended parameters. This could lead to a variety of malicious outcomes, such as bypassing security checks, altering data, or manipulating the application's behavior.\n\n**Note:**\nFollowing our established security policy, we attempted to contact the maintainer regarding this vulnerability, but haven't received a response.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "cloudinary"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.7.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-12613"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/cloudinary/cloudinary_npm/pull/709"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/cloudinary/cloudinary_npm/commit/ec4b65f2b3461365c569198ed6d2cfa61cca4050"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/cloudinary/cloudinary_npm"
  }, {
    "type" : "WEB",
    "url" : "https://security.snyk.io/vuln/SNYK-JS-CLOUDINARY-10495740"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-88" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-11-12T23:41:30Z",
    "nvd_published_at" : "2025-11-10T05:15:42Z"
  }
}