dbcve.org
PhotoshopApplication · Adobe

CVE-2024-43760

HIGH · 7.8 CVSS v3.1 Published 2024-09-13
Fix available
A fix is available. Upgrade to 24.7.5 / 25.12 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.4, 25.11 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.

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 contains an out-of-bounds write vulnerability in its file parsing logic. When processing a specially crafted malicious file, the application writes data beyond allocated memory boundaries, potentially allowing an attacker to overwrite memory and execute arbitrary code in the context of the current user.

MitigationApply the vendor security update (Photoshop 24.7.5 and 25.12 or later) immediately. Until patched, warn users against opening untrusted or unexpected image files, as exploitation requires only that a victim open a malicious file.

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.7.5>= 25.0, < 25.12

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. Check Photoshop version on Windows
    Open Photoshop, go to Help > About Photoshop, or check the Windows Registry at HKEY_CLASSES_ROOT\Photoshop.Application\DefaultIcon or HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Photoshop\Version
    Affected if The version shown is earlier than 24.7.5, or is 25.0 through 25.11.x
  2. Check Photoshop version on macOS
    Open Photoshop, go to Photoshop > About Photoshop, or check the application bundle info at /Applications/Adobe Photoshop [version]/Adobe Photoshop.app/Contents/Info.plist for CFBundleShortVersionString
    Affected if The version shown is earlier than 24.7.5, or is 25.0 through 25.11.x
  3. Identify exact version number
    Note the full version number (for example 24.7.0, 25.7.0, or 25.12.0) from the About dialog or registry/plist
    Affected if The version is less than 24.7.5 (such as 24.7.4 or 24.6.0) OR the version is 25.0.0 through 25.11.x (such as 25.7.0 or 25.10.0)
  4. Confirm file parsing usage
    This vulnerability is triggered when Photoshop parses specially crafted image files. No special configuration check is needed; any user who can open files in Photoshop is potentially affected if the version is vulnerable.
    Affected if The installed Photoshop version falls within the affected ranges and users can open external files

You are affected if your installed Photoshop version is earlier than 24.7.5 (24.x versions below 24.7.5) OR is version 25.0.0 through 25.11.x. Versions 24.7.5 and later, or 25.12.0 and later, are not affected.

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.5 / 25.12 or later
Fixed in 24.7.525.12
Interim mitigation

Apply the vendor security update (Photoshop 24.7.5 and 25.12 or later) immediately. Until patched, warn users against opening untrusted or unexpected image files, as exploitation requires only that a victim open a malicious file.

Recommended fix High confidence

Photoshop 24.7.5 (for 24.x branch) or Photoshop 25.12 (for 25.x branch)

  1. 1. Check current Photoshop version by going to Help > About Photoshop in the application menu
  2. 2. Determine which version branch you are on (24.x or 25.x)
  3. 3. For users on version 24.x: Upgrade to version 24.7.5 or later
  4. 4. For users on version 25.x: Upgrade to version 25.12 or later
  5. 5. Download the update from the official Adobe website or use the Adobe Creative Cloud desktop application to install the update
  6. 6. After installation, verify the version by checking Help > About Photoshop to confirm the update was successful
Caveat Minor: Standard update; review Adobe release notes for any changes to features or workflows

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-43760 — 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-43760 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