dbcve.org
PhotoshopApplication · Adobe

CVE-2025-30324

HIGH · 7.8 CVSS v3.1 Published 2025-05-13
Fix available
A fix is available. Upgrade to 25.12.3 / 26.6 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.5, 25.12.2 and earlier are affected by an Integer Underflow (Wrap or Wraparound) 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

This is an integer underflow (wrap/wraparound) vulnerability in Adobe Photoshop Desktop versions 26.5, 25.12.2 and earlier. The vulnerability occurs when the software processes maliciously crafted files, causing an arithmetic operation to wrap around and produce an unexpectedly small value, leading to memory corruption and potential arbitrary code execution in the current user's context.

MitigationUpdate Photoshop Desktop to versions later than 26.5 and 25.12.2 when patches become available. Avoid opening untrusted or suspicious files in Photoshop 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.3>= 26.0, < 26.6

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. Check if Adobe Photoshop is installed
    Locate Photoshop installation directory or check system registry for Adobe Photoshop entries
    Affected if Photoshop is found on the system
  2. Determine installed Photoshop version
    Open Photoshop, go to Help > About Photoshop, or check the version in the application executable properties
    Affected if A version number is displayed
  3. Compare version to affected range for 25.x
    Compare your installed version against the range 25.0 through 25.12.2 (versions below 25.12.3 are affected)
    Affected if Installed version is 25.0 through 25.12.2 inclusive
  4. Compare version to affected range for 26.x
    Compare your installed version against the range 26.0 through 26.5 (versions below 26.6 are affected)
    Affected if Installed version is 26.0 through 26.5 inclusive
  5. Verify vulnerable condition exists
    The vulnerability triggers when processing files - this is inherent to Photoshop's core functionality, so any affected version is potentially vulnerable when opening untrusted files
    Affected if Affected version is installed and the application is used to open files

You are affected if Photoshop is installed and the version falls within 25.0 to 25.12.2 or 26.0 to 26.5, since these versions contain the integer underflow flaw when processing files.

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.3 / 26.6 or later
Fixed in 25.12.326.6
Interim mitigation

Update Photoshop Desktop to versions later than 26.5 and 25.12.2 when patches become available. Avoid opening untrusted or suspicious files in Photoshop until the update is applied.

Recommended fix High confidence

Photoshop 25.12.3 (for 25.x branch) or 26.6 (for 26.x branch) or later

  1. Open Adobe Photoshop and go to Help > About Photoshop to check current version
  2. If version is 25.x and below 25.12.3, or 26.x and below 26.6, proceed with update
  3. Open Adobe Creative Cloud desktop application
  4. Navigate to the Photoshop application in your CC library
  5. Click Update to download and install the fixed version, or manually download from helpx.adobe.com/photoshop/kb/photoshop-security-update.html

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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