dbcve.org
PhotoshopApplication · Adobe

CVE-2024-34117

HIGH · 7.8 CVSS v3.1 Published 2024-08-14
Fix available
A fix is available. Upgrade to 24.7.4 / 25.11 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
Photoshop Desktop versions 24.7.3, 25.9.1 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 confidence

Adobe Photoshop Desktop versions 24.7.3, 25.9.1 and earlier contain a Use After Free (UAF) vulnerability. This memory corruption flaw allows arbitrary code execution when a victim opens a specially crafted malicious file, as the attacker can manipulate freed memory that the application still references.

MitigationUpdate Adobe Photoshop to version 24.7.4 or 25.9.2 or later to patch the vulnerability. Avoid opening files from untrusted or unknown sources until the update is applied.

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
PhotoshopApplication
Affected:>= 24.2, < 24.7.4>= 25.0, < 25.11

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. Locate installed Adobe Photoshop version
    Open Photoshop, go to Help > About Photoshop, or on Windows check Programs and Features, or on Mac check /Applications folder for the version year
    Affected if The displayed version is visible for comparison to affected ranges
  2. Compare version to affected 24.x range
    If using version 24.x, verify the exact build number: 24.2 through 24.7.3 are affected; versions below 24.2 or 24.7.4+ are not in this range
    Affected if Installed version is 24.2 through 24.7.3 (inclusive)
  3. Compare version to affected 25.x range
    If using version 25.x, verify the exact build number: 25.0 through 25.9.1 are affected; versions below 25.0 or 25.9.2+ are not in this range
    Affected if Installed version is 25.0 through 25.9.1 (inclusive)
  4. Confirm vulnerability trigger condition
    This vulnerability is triggered when opening a specially crafted malicious file - the flaw exists in the file parsing code regardless of system configuration
    Affected if The affected Photoshop version is installed and the application is used to open files

User is affected if Adobe Photoshop version is 24.2 through 24.7.3 OR 25.0 through 25.9.1 (any version in these two ranges, regardless of OS settings or configurations).

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 24.7.4 / 25.11 or later
Fixed in 24.7.425.11
Interim mitigation

Update Adobe Photoshop to version 24.7.4 or 25.9.2 or later to patch the vulnerability. Avoid opening files from untrusted or unknown sources until the update is applied.

Recommended fix High confidence

Photoshop 24.7.4 or later for 24.x line; Photoshop 25.11 or later for 25.x line

  1. 1. Determine current Adobe Photoshop version by opening Photoshop and navigating to Help > About Photoshop
  2. 2. If running version 24.x (24.2 through 24.7.3), upgrade to version 24.7.4 or later
  3. 3. If running version 25.x (25.0 through 25.10), upgrade to version 25.11 or later
  4. 4. Download the appropriate fixed version from the official Adobe website at adobe.com
  5. 5. Install the updated version and restart Photoshop
  6. 6. Verify the installed version matches a fixed release (24.7.4+ or 25.11+)
Caveat Standard version upgrade; minimal risk; always backup custom presets and settings before upgrading major versions

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

Fix this in Photoshop Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-2024-34117 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