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.
Product
Adobe Lightroom Desktop vulnerabilities
5 published CVES affecting Adobe Lightroom Desktop, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 5
- Critical
- 0
- High
- 4
- Medium
- 1
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest Adobe Lightroom Desktop CVEs
Newest publication first
-
HighCVSS 7.8 EPSS 0.17%
-
HighCVSS 7.8 EPSS 0.22%
Lightroom Desktop versions 8.2 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.
-
MediumCVSS 5.5 EPSS 0.23%
Lightroom Desktop versions 7.4.1, 13.5, 12.5.1 and earlier are affected by an out-of-bounds read vulnerability that could lead to disclosure of sensitive memory. An attacker could leverage this vulnerability to bypass mitigations such as ASLR. Exploitation of this issue requires...
-
HighCVSS 7.8 EPSS 0.33%
Lightroom Desktop versions 7.1.2 and earlier are affected by an Untrusted Search Path vulnerability that could result in arbitrary code execution in the context of the current user. If the application uses a search path to locate critical resources such as programs, then an attac...
-
CVE-2021-43753 Adobe Lightroom TIF File Parsing Use-After-Free Information Disclosure Vulnerability
PublishedHighCVSS 7.8 EPSS 0.45%Adobe Lightroom versions 4.4 (and earlier) are affected by a use-after-free vulnerability in the processing of parsing TIF files that could result in privilege escalation. Exploitation of this issue requires user interaction in that a victim must open a malicious file.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.