CVE-2024-52997
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 · uneditedPhotoshop Desktop versions 26.0 and earlier are affected by a Use After Free 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 confidenceAdobe Photoshop Desktop versions 26.0 and earlier contain a Use After Free vulnerability that can be triggered when a user opens a malicious file. The vulnerability allows arbitrary code execution in the context of the current user due to improper memory management in file parsing operations.
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= 26.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Photoshop versionOpen Photoshop, go to Help > About Photoshop, or check Programs and Features to view the installed version numberAffected if Version is 26.0 or earlier (any version up to and including 26.0)
-
Verify version via command lineRun 'reg query "HKLM\SOFTWARE\Adobe\Photoshop\InstallVersion" /v Version' in Command Prompt to read the registry valueAffected if The returned version value is 26.0 or lower
-
Check multiple Photoshop installationsCheck both 32-bit and 64-bit registry keys: HKLM\SOFTWARE\Adobe\Photoshop and HKLM\SOFTWARE\WOW6432Node\Adobe\PhotoshopAffected if Any installed copy of Photoshop is version 26.0 or earlier
You are affected if any installed Adobe Photoshop Desktop version is 26.0 or earlier, since the Use After Free vulnerability triggers during file parsing operations on malicious files.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate Photoshop to version 26.1 or later. Avoid opening files from untrusted sources until the patch is applied.
Photoshop 26.1 or later (2024 release)
- 1. Close Adobe Photoshop completely if it is currently running
- 2. Open Adobe Creative Cloud desktop application
- 3. Navigate to the Apps tab or find Photoshop in your installed applications
- 4. Click on the update option next to Photoshop to install the latest version
- 5. Alternatively, download the latest Photoshop version from the official Adobe website
- 6. After updating, verify the installed version matches or exceeds the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-52997 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-52997 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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