PhotoshopApplication · Adobe

CVE-2025-49570

HIGH · 7.8 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 25.12.4 / 26.9 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 25.12.3, 26.8 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 · moderate confidence

Adobe Photoshop Desktop versions 25.12.3, 26.8 and earlier contain an out-of-bounds write vulnerability that can be triggered when a user opens a maliciously crafted file, potentially allowing arbitrary code execution in the context of the current user.

MitigationUpdate Photoshop to the latest patched version beyond 25.12.3 and 26.8; advise users to avoid opening files from untrusted sources.

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:>= 25.0, < 25.12.4>= 26.0, < 26.9

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 Photoshop version
    Open Photoshop, go to Help > About Photoshop, or right-click the Photoshop executable and select Properties > Details to view the Product Version
    Affected if Version shows 25.x (any version from 25.0 to 25.12.3) or 26.x (any version from 26.0 to 26.8)
  2. Compare version against vulnerable ranges
    Check if the installed version falls within these ranges: 25.0 to 25.12.3 (inclusive), or 26.0 to 26.8 (inclusive)
    Affected if Version is greater than or equal to 25.0 and less than 25.12.4, OR greater than or equal to 26.0 and less than 26.9
  3. Identify the attack vector
    Understand that this vulnerability is triggered specifically when a user opens a maliciously crafted image file in Photoshop
    Affected if Users in the environment open files from untrusted or unknown sources using vulnerable Photoshop versions

The environment is affected if any installed instance of Adobe Photoshop is version 25.0 through 25.12.3 or version 26.0 through 26.8, since opening a specially crafted file could trigger the out-of-bounds write vulnerability in these versions.

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 25.12.4 / 26.9 or later
Fixed in 25.12.426.9
Interim mitigation

Update Photoshop to the latest patched version beyond 25.12.3 and 26.8; advise users to avoid opening files from untrusted sources.

Recommended fix High confidence

Photoshop 25.12.4 (for 25.x branch) or Photoshop 26.9 (for 26.x branch)

  1. Close Adobe Photoshop completely before updating
  2. Open Adobe Creative Cloud desktop application
  3. Navigate to the 'Apps' or 'Updates' section in the left sidebar
  4. Locate Adobe Photoshop in the list of installed apps
  5. Click the 'Update' button next to Photoshop to install the latest version
  6. Alternatively, visit the Adobe Photoshop download page at adobe.com and download the latest version for your subscription tier
  7. Restart Photoshop after the update completes
  8. Verify the installed version by going to Help > About Photoshop to confirm you are on 25.12.4 or 26.9

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

Fix this in Photoshop Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-49570 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-49570 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