CVE-2025-30325
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 26.5, 25.12.2 and earlier are affected by an Integer Overflow 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 confidenceAdobe Photoshop Desktop versions 26.5, 25.12.2 and earlier contain an Integer Overflow or Wraparound vulnerability that allows arbitrary code execution in the context of the current user. Exploitation requires a victim to open a maliciously crafted file, making this a client-side code execution vulnerability.
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>= 25.0, < 25.12.3>= 26.0, < 26.6CVSS 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.
-
Locate Adobe Photoshop installationOpen Adobe Photoshop, then go to Help > About Photoshop to display the version number. Alternatively, check the application file properties (right-click Photoshop.exe > Properties > Details) on Windows, or Get Info on macOS.Affected if Photoshop is installed on the system
-
Identify the major version lineNote whether the installed version begins with 25.x (e.g., 25.12.2) or 26.x (e.g., 26.5). This determines which vulnerability range applies.Affected if The version starts with 25 or 26
-
Compare against affected version rangesCheck if the installed version falls within these ranges: 25.0 through 25.12.2 (inclusive), or 26.0 through 26.5 (inclusive). Any version below 25.12.3 in the 25.x line, or below 26.6 in the 26.x line, is vulnerable.Affected if Installed version is >= 25.0 and < 25.12.3, OR >= 26.0 and < 26.6
-
Determine exposure to malicious filesAssess whether the user opens image files (such as PSD, JPEG, PNG, TIFF, or other formats supported by Photoshop) from untrusted or unknown sources, as exploitation requires opening a maliciously crafted file.Affected if Users open files from untrusted sources without validation
A user is affected if they have Adobe Photoshop version 25.0 through 25.12.2 or version 26.0 through 26.5 installed AND they open untrusted files, since exploitation requires opening a maliciously crafted file.
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 · scoped25.12.326.6
Update Photoshop to a version newer than 26.5 or 25.12.2 using Adobe's official update mechanism, and avoid opening files from untrusted sources.
Photoshop 25.12.3 (or later 25.x) / Photoshop 26.6 (or later 26.x)
- Close Photoshop completely before updating
- Open Adobe Creative Cloud desktop application
- Navigate to the Photoshop application in Creative Cloud
- Click on 'Update' or 'Install' to install the latest version
- For version 25.x line: Ensure update to version 25.12.3 or later
- For version 26.x line: Ensure update to version 26.6 or later
- After update completes, verify the installed version by opening Photoshop and checking Help > About Photoshop
- Confirm the version number matches or exceeds the fixed release for your product line
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30325 — 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-2025-30325 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