dbcve.org
PhotoshopApplication · Adobe

CVE-2024-45108

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 file processing logic that allows memory corruption. When a user opens a specially crafted malicious file, the vulnerability can be exploited to achieve arbitrary code execution within the context of the current user session.

MitigationUpdate Photoshop to a patched version once released. Until then, instruct users not to open untrusted or unexpected image files, and consider implementing file-type restrictions or additional monitoring for suspicious file attachments.

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. Locate installed Adobe Photoshop version
    Open Adobe Photoshop, then go to Help > About Photoshop (or use Command/Ctrl+K to open Preferences and check the Version information panel). Alternatively, on Windows check Add/Remove Programs or the file properties of the Photoshop.exe binary in the installation directory.
    Affected if The displayed version is less than 24.7.5, or is between 25.0 and 25.12 inclusive.
  2. Confirm Photoshop installation path and executable
    On Windows, common paths are C:\Program Files\Adobe\Adobe Photoshop [Version]\Photoshop.exe. On macOS, check /Applications/Adobe Photoshop [Version]. Right-click the executable and view Properties to see the version.
    Affected if The executable exists and its version matches an affected release.
  3. Compare version number against CVE ranges
    Take the identified version number (for example, 24.7.0 or 25.5) and compare it manually to the affected ranges: versions below 24.7.5 are vulnerable, and versions 25.0 through 25.11.x are vulnerable.
    Affected if Your installed version falls within < 24.7.5 or >= 25.0 and < 25.12.

You are affected if Photoshop is installed and the version number is below 24.7.5 or between 25.0 and 25.12.

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

Update Photoshop to a patched version once released. Until then, instruct users not to open untrusted or unexpected image files, and consider implementing file-type restrictions or additional monitoring for suspicious file attachments.

Recommended fix High confidence

Photoshop 24.7.5 or later for version 24.x branch; Photoshop 25.12 or later for version 25.x branch

  1. 1. Close Adobe Photoshop if it is currently running
  2. 2. Open Adobe Creative Cloud desktop application
  3. 3. Navigate to the 'Apps' or 'Products' section
  4. 4. Find Adobe Photoshop in the installed applications list
  5. 5. Click on the 'Update' button next to Photoshop, or check for available updates
  6. 6. Wait for the update to download and install completely
  7. 7. Verify the installed version matches the fixed release (24.7.5 or later for version 24.x, 25.12 or later for version 25.x)
  8. 8. Reopen Photoshop and confirm it launches successfully
Caveat Standard Adobe update; ensure system meets minimum requirements for the new version

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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