LightroomApplication · Adobe

CVE-2026-21349

HIGH · 7.8 CVSS v3.1 Published 2026-02-10
Fix available
A fix is available. Upgrade to 14.5.2 / 15.1.1 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
Lightroom Desktop versions 15.1 and earlier are affected by an out-of-bounds write vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.

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 · high confidence

Lightroom Desktop versions 15.1 and earlier contain an out-of-bounds write vulnerability that could allow arbitrary code execution when a user opens a maliciously crafted file, running with the privileges of the current user.

MitigationUpdate Lightroom Desktop to a version newer than 15.1 when a patch is available, and avoid opening untrusted or unexpected image files from unverified sources.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LightroomApplication
Affected:< 14.5.2>= 15.0, < 15.1.1

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Confirm Lightroom Desktop installation
    Locate Adobe Lightroom Desktop application on your system (Windows: Program Files/Adobe/Adobe Lightroom, macOS: /Applications/Adobe Lightroom)
    Affected if The Lightroom Desktop application directory exists on the system
  2. Identify installed Lightroom version
    Open Lightroom Desktop and navigate to Help > About Adobe Lightroom (Windows) or Lightroom > About Adobe Lightroom (macOS) to display the version number
    Affected if A version number such as 14.x.x or 15.x.x is displayed
  3. Compare version against affected ranges
    Check if your installed version is less than 14.5.2, or between 15.0 and 15.1.1 (including 15.0.x and 15.1.0)
    Affected if Installed version is < 14.5.2 OR (>= 15.0 AND < 15.1.1)
  4. Assess exposure to malicious files
    Determine whether Lightroom Desktop is used to open image files from external or untrusted sources
    Affected if Users routinely open image files from unverified or unexpected sources using Lightroom Desktop

You are affected if Lightroom Desktop version is either below 14.5.2 or falls within the 15.0 to 15.1.1 range, and users open files with the application.

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.

dbcve · scoped
Upgrade available Upgrade to 14.5.2 / 15.1.1 or later
Fixed in 14.5.215.1.1
Interim mitigation

Update Lightroom Desktop to a version newer than 15.1 when a patch is available, and avoid opening untrusted or unexpected image files from unverified sources.

Recommended fix High confidence

Lightroom 14.5.2 (for versions < 14.5.2) or Lightroom 15.1.1 (for versions >= 15.0 and < 15.1.1)

  1. Open Adobe Creative Cloud desktop application on your computer
  2. Navigate to the Apps section and find Lightroom in your installed apps
  3. Click on the update button next to Lightroom, or select 'Update' to install the latest version
  4. Alternatively, visit helpx.adobe.com and download the latest Lightroom version from the Adobe downloads page
  5. Restart Lightroom after the update completes
  6. Verify the installed version by going to Help > About Lightroom to confirm you have version 14.5.2 or 15.1.1
Caveat Adobe updates typically include bug fixes and security patches; review release notes for any plugin or preset compatibility changes before updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Lightroom Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-21349 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