Code execution via malicious-file deserialization
Published Aug 11, 2026 · Updated Aug 11, 2026
Deserialization of untrusted data in Adobe Lightroom Classic 15.4 and earlier allows attackers to execute code through a malicious file. Adobe identifies unsafe deserialization but has not disclosed the affected file parser, data format, or operation performed on serialized input. Exploitation requires a local user to open the crafted file, after which code runs in that user's context and can cross a security scope boundary.
Summary
What happened
Deserialization of untrusted data in Adobe Lightroom Classic 15.4 and earlier allows attackers to execute code through a malicious file. Adobe identifies unsafe deserialization but has not disclosed the affected file parser, data format, or operation performed on serialized input. Exploitation requires a local user to open the crafted file, after which code runs in that user's context and can cross a security scope boundary.
The record
- CVE
- CVE-2026-48397
- Published
- Aug 11, 2026
- Updated
- Aug 11, 2026
- Vendor
- Adobe
- Product
- Lightroom Classic
- Classifications
- CWE-502, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 11, 2026CVE publishedPublication date reported by the CVE source.
- Aug 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=15.4, 15.4.1, 15.3, 15.3.1, 15.2, 15.2.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo