dbcve.org
PhotoshopApplication · Adobe

CVE-2025-27198

HIGH · 7.8 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 25.12.2 / 26.5 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.1, 26.4.1 and earlier are affected by a Heap-based Buffer Overflow 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 versions 25.12.1, 26.4.1 and earlier contain a heap-based buffer overflow vulnerability that can be triggered when a user opens a maliciously crafted file, leading to arbitrary code execution in the context of the current user.

MitigationUpdate Photoshop to version 25.12.2 or later (for version 25.x) and 26.4.2 or later (for version 26.x). Users should avoid opening untrusted files until the update is applied.

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.2>= 26.0, < 26.5

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 Adobe Photoshop is installed
    Locate the Photoshop executable (Photoshop.exe on Windows, Photoshop on Mac) in the application directory, typically C:\Program Files\Adobe\Adobe Photoshop <version> on Windows or /Applications/Adobe Photoshop <version> on Mac
    Affected if Photoshop is not installed on the system
  2. Determine the installed Photoshop version number
    On Windows: right-click Photoshop.exe, select Properties, then view the File Version on the Details tab. On Mac: right-click Photoshop.app, select Get Info, and view the Version under General. Alternatively, open Photoshop and go to Help > About Photoshop
    Affected if Unable to retrieve a version number from the Photoshop installation
  3. Compare the version against the affected ranges
    If the version starts with 25.x, check if it is less than 25.12.2. If it starts with 26.x, check if it is less than 26.5
    Affected if The installed version falls within 25.0 to 25.12.1 (inclusive) or 26.0 to 26.4.x (inclusive)
  4. Confirm the vulnerability trigger condition
    This vulnerability is triggered when a user opens a maliciously crafted file in Photoshop. Check if users have the ability to open files from untrusted sources
    Affected if Users can open arbitrary files in Photoshop and the version is in the affected range

The system is affected if Adobe Photoshop is installed with a version between 25.0 and 25.12.1 (inclusive) or between 26.0 and 26.4.x (inclusive) and users may open files from untrusted sources.

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.2 / 26.5 or later
Fixed in 25.12.226.5
Interim mitigation

Update Photoshop to version 25.12.2 or later (for version 25.x) and 26.4.2 or later (for version 26.x). Users should avoid opening untrusted files until the update is applied.

Recommended fix High confidence

Photoshop 25.12.2 or later for 25.x branch; Photoshop 26.5 or later for 26.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 section
  4. 4. Find Adobe Photoshop in your installed apps list
  5. 5. Click on the update button next to Photoshop to install the latest version
  6. 6. Alternatively, download the latest Photoshop version from the Adobe website directly
  7. 7. Verify the installed version by opening Photoshop and going to Help > About Photoshop
Caveat Standard Photoshop update - ensure compatibility with existing workflows and plugins before production use

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 / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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