dbcve.org
PhotoshopApplication · Adobe

CVE-2025-61819

HIGH · 7.8 CVSS v3.1 Published 2025-11-11
Fix available
A fix is available. Upgrade to 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 26.8.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

A heap-based buffer overflow vulnerability in Adobe Photoshop Desktop versions 26.8.1 and earlier allows arbitrary code execution through a maliciously crafted file. The attacker must trick the victim into opening the file, and code executes with the privileges of the current user.

MitigationUpdate Photoshop to a version newer than 26.8.1. Avoid opening untrusted or unexpected files in Photoshop.

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:< 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. Confirm Adobe Photoshop is installed
    Locate Photoshop application on the system - on Windows check Program Files or Program Files (x86) folders for an Adobe Photoshop folder, or on macOS check the /Applications folder for Adobe Photoshop.app
    Affected if Adobe Photoshop Desktop is found installed on the system
  2. Determine installed Photoshop version
    Open Photoshop, then go to Help > About Photoshop (Windows) or Photoshop > About Photoshop (macOS) to display the version number, or check the version in the application installer if available
    Affected if The displayed version is 26.8.1 or earlier, or any version below 26.9
  3. Compare version to affected range
    Review the version number identified in step 2 against the affected range: versions earlier than 26.9 are vulnerable
    Affected if The installed version is earlier than 26.9 (for example 26.8.1, 26.7.0, earlier releases)
  4. Assess file opening behavior
    Determine whether the user or others with access to this system open Photoshop files (such as .psd, .psb, or image files) from untrusted or unexpected sources
    Affected if Users routinely open files from untrusted or unknown sources in Photoshop, as the exploit requires the victim to open a maliciously crafted file

The system is affected if Adobe Photoshop Desktop is installed with any version earlier than 26.9 and the application is used to open files, including those 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 26.9 or later
Fixed in 26.9
Interim mitigation

Update Photoshop to a version newer than 26.8.1. Avoid opening untrusted or unexpected files in Photoshop.

Recommended fix High confidence

Adobe Photoshop 26.9

  1. Open Adobe Creative Cloud desktop application on your system
  2. Navigate to the 'Apps' or 'Updates' section
  3. Find Adobe Photoshop in the list of available updates
  4. Click 'Update' or 'Install' to upgrade to the latest version
  5. Alternatively, open Photoshop and go to Help > Updates to trigger the update check
  6. Confirm the update installs Photoshop version 26.9 or later
  7. Verify the installed version by going to Help > About Photoshop and confirm the version number is 26.9 or higher
Caveat Minor version upgrade within same major version; default settings preserved; verify compatibility with custom plugins or workflows after update

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

Fix this in Photoshop Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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