dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-24560

MEDIUM · 5.4 CVSS v3.1 Developing Published 2026-01-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Missing Authorization vulnerability in Cloudinary Cloudinary cloudinary-image-management-and-manipulation-in-the-cloud-cdn allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Cloudinary: from n/a through <= 3.3.2.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · low confidence

Missing Authorization vulnerability in the Cloudinary SDK (versions through 3.3.2) allows attackers to access resources or perform operations without proper authorization due to incorrectly configured access control security levels.

MitigationReview and enforce proper authorization checks on all API endpoints and resources, and update to a patched version if available from Cloudinary.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Cloudinary SDK installation
    Run 'pip show cloudinary' for Python or 'npm list cloudinary' for Node.js to find the installed package and version
    Affected if The package is present and version is 3.3.2 or lower
  2. Confirm SDK version range
    Compare the installed version number against the affected range: versions 3.3.2 and below are affected
    Affected if Installed version is 3.3.2 or any earlier version (e.g., 3.3.1, 3.3.0, 2.x)
  3. Locate Cloudinary configuration
    Search project codebase for Cloudinary configuration files or initialization code - look for 'cloudinary.config' calls or config objects containing cloud_name, api_key, api_secret
    Affected if Cloudinary SDK is configured and in use
  4. Inspect access control settings
    Examine Cloudinary configuration for security-related options such as 'secure', 'strict', 'access_control', or similar security level settings - check if they are missing, disabled, or set to overly permissive values
    Affected if Security access control options are missing, disabled, or configured permissively (e.g., set to 'false', 'disabled', or 'allow_all')

You are affected if the Cloudinary SDK version is 3.3.2 or lower AND access control security settings are missing or misconfigured in your implementation

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Review and enforce proper authorization checks on all API endpoints and resources, and update to a patched version if available from Cloudinary.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24560 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-24560 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data