CVE-2024-45109
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 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 confidenceAdobe Photoshop Desktop versions 24.7.4, 25.11 and earlier contain an out-of-bounds write vulnerability that allows arbitrary code execution in the context of the current user. Successful exploitation requires a victim to 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< 24.7.5>= 25.0, < 25.12CVSS 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 Photoshop version on WindowsOpen Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Photoshop\InstallVersion. Check the value of the (Default) or Version key.Affected if The version shown is earlier than 24.7.5 OR falls between 25.0 and 25.11 inclusive.
-
Check Photoshop version via Help menuOpen Photoshop, then go to Help > About Photoshop. The version number is displayed in the dialog that appears.Affected if The displayed version is earlier than 24.7.5 OR falls between 25.0 and 25.11 inclusive.
-
Check Photoshop version on macOSOpen Finder, navigate to Applications > Adobe Photoshop, right-click the application, select Get Info, and look at the Version field under General information.Affected if The version shown is earlier than 24.7.5 OR falls between 25.0 and 25.11 inclusive.
-
Verify file association handlingCheck if Photoshop is configured to automatically open files. Review file associations in Photoshop preferences under File Handling, or check if the system opens files directly with Photoshop without user confirmation.Affected if Automatic file opening is enabled and the system runs vulnerable Photoshop version, making malicious files a direct threat.
You are affected if your installed Adobe Photoshop version is 24.7.4 or earlier, or any version from 25.0 through 25.11.
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 · scoped24.7.525.12
Update Photoshop to the latest patched version. Users should avoid opening untrusted or unexpected files until the update is applied.
Photoshop 24.7.5 (or later for 24.x branch) or Photoshop 25.12 (or later for 25.x branch)
- 1. Close Adobe Photoshop if it is currently running
- 2. Open Adobe Creative Cloud desktop application or navigate to the Adobe Photoshop download page at helpx.adobe.com
- 3. Locate Adobe Photoshop in your installed applications
- 4. Click Update or Install to download and install the latest version
- 5. For version 24.x users: Ensure the update installs version 24.7.5 or later
- 6. For version 25.x users: Ensure the update installs version 25.12 or later
- 7. Restart Photoshop after the update completes
- 8. Verify the installed version by going to Help > About Photoshop
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45109 — 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-45109 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