dbcve.org
PhotoshopApplication · Adobe

CVE-2024-49514

HIGH · 7.8 CVSS v3.1 Published 2024-11-12
Fix available
A fix is available. Upgrade to 24.7.4 / 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.3, 25.11 and earlier are affected by an Integer Underflow (Wrap or Wraparound) 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

Integer underflow vulnerability in Adobe Photoshop Desktop allows arbitrary code execution when a user opens a specially crafted malicious file, exploiting the wraparound behavior to corrupt memory and achieve code execution in the current user's context.

MitigationUpdate Photoshop Desktop to version 25.12 or later. Additionally, implement user training to avoid opening files from untrusted sources, as exploitation requires user interaction.

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.4>= 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. Verify Photoshop is installed
    Check for Adobe Photoshop installation - on Windows look in Program Files/Adobe or check Start Menu, on macOS check /Applications folder for Photoshop.app
    Affected if Photoshop is not installed on the system
  2. Find installed Photoshop version number
    Open Photoshop, go to Help > About Photoshop (Windows) or Photoshop > About Photoshop (macOS), or check the version in the application properties. Alternatively, check the file version of Photoshop.exe in the installation directory
    Affected if Cannot determine version number - version check inconclusive
  3. Compare against affected version ranges
    Compare your installed version to the affected ranges: versions 24.x below 24.7.4, and versions 25.x below 25.12. For example, 24.7.3 is affected, 24.7.4 is not; 25.0 is affected, 25.12 is not
    Affected if Installed version is 24.7.3 or earlier OR is 25.0 through 25.11 (any version 25.x below 25.12)

Your environment is affected if Adobe Photoshop is installed and the installed version falls below 24.7.4 for the 24.x line or below 25.12 for the 25.x line.

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.12 or later
Fixed in 24.7.425.12
Interim mitigation

Update Photoshop Desktop to version 25.12 or later. Additionally, implement user training to avoid opening files from untrusted sources, as exploitation requires user interaction.

Recommended fix High confidence

Photoshop 24.7.4 (for version 24.x users) or Photoshop 25.12 (for version 25.x users)

  1. Open Adobe Photoshop and go to Help > About Photoshop to check your current version
  2. If your version is 24.x.x and below 24.7.4, or 25.x.x and below 25.12, you need to update
  3. Open Adobe Creative Cloud desktop application and navigate to the Apps section
  4. Find Adobe Photoshop in your installed apps list
  5. Click the Update button next to Photoshop to install the latest version
  6. Alternatively, download the update directly from helpx.adobe.com
  7. Restart Photoshop after the update completes
  8. Verify the update was successful by checking Help > About Photoshop shows version 24.7.4 or higher, or 25.12 or higher

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

Fix this in Photoshop Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-49514 — 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-49514 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