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.
Security readout for executives and security teams
Plain-English summary
A malicious file opened in Adobe Lightroom Desktop could corrupt memory and let an attacker run code with the victim’s user permissions. The risk includes data theft, file modification, and disruption, but exploitation requires the victim to open the file.
Executive priority
Treat this as a high-priority workstation update, especially for creative teams handling externally supplied files. It is not described as remotely exploitable without user action, and active exploitation is not established in the supplied evidence, so response should be prompt and risk-based rather than emergency-wide containment.
Technical view
CVE-2026-21349 is a CWE-787 out-of-bounds write in Lightroom Desktop 15.1 and earlier. It has CVSS 3.1 score 7.8 and may enable arbitrary code execution as the current user. The supplied structured version list is inconsistent with the description, so exact affected-version mapping should be confirmed against Adobe’s advisory.
Likely exposure
Workstations running Lightroom Desktop 15.1 or earlier are potentially exposed, particularly where users receive or import files from external or untrusted sources. The vulnerability is local and requires user interaction; network reachability alone does not establish exposure.
Exploitation context
The victim must open a malicious file. The source bundle does not identify this CVE as CISA KEV-listed and provides no cited evidence of active exploitation. That absence should not be interpreted as proof that exploitation is impossible or has never occurred.
Researcher notes
The core condition is an out-of-bounds write triggered through malicious-file processing, with code execution scoped to the current user. CVSS indicates local attack vector, low complexity, no privileges, required user interaction, unchanged scope, and high confidentiality, integrity, and availability impact. The bundle’s affected-version array conflicts with its description and requires vendor confirmation.
Mitigation direction
Check Adobe advisory APSB26-06 for the confirmed fixed release and update Lightroom Desktop promptly.
Prioritize systems whose users routinely process files from customers, partners, public submissions, or other untrusted sources.
Until updated, discourage opening unexpected Lightroom-compatible files and verify their origin through a separate communication channel.
Use endpoint protection and least-privilege controls to limit consequences if malicious code executes.
Validation and detection
Inventory installed Lightroom Desktop versions and identify systems running 15.1 or earlier.
Confirm the installed version after remediation matches a release Adobe identifies as fixed.
Review software deployment records for update failures, deferred installations, and unmanaged endpoints.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-787: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-787 · source CWE mapping
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.