Cloudinary Node SDK is vulnerable to Arbitrary Argument Injection through parameters that include an ampersand

published 2025-11-10 11 mo ago modified 2026-10-19 21 d ago also GHSA-g4mf-96x5-5m2c , EUVD-2025-44030

cvss: 8.6; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 33%
public exploits: 0; none known

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.

Patch / fix

fixed in 2 links 2

npm cloudinary 2.7.0
n/a cloudinary 2.7.0

github.com/cloudinary/cloudinary_npm@ec4b65f commit
github.com/cloudinary/cloudinary_npm#709 pull request

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: partial
Assessed: 11 mo ago (2025-11-10)

Exploit prediction

0.39% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	4.0	8.8	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
CNA	3.1	8.6	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L
CNA	4.0	8.8	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/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
GitHub	3.1	8.6	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L

Affected packages

ecosystem	package	affected	fixed in
npm	cloudinary	<2.7.0	2.7.0

Affected products

n/a cloudinary

Classification

Weakness

CWE-88 Improper Neutralization of Argument Delimiters in a Command

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary