dbcve.org
PhotoshopApplication · Adobe

CVE-2022-28275

HIGH · 7.8 CVSS v3.0 Published 2022-05-06
Fix available
A fix is available. Upgrade to after 23.2.2 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
Adobe Photoshop versions 22.5.6 (and earlier) and 23.2.2 (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 · high confidence

Adobe Photoshop contains an out-of-bounds write vulnerability where opening a specially crafted malicious file triggers memory corruption, potentially allowing arbitrary code execution with the current user's privileges.

MitigationUpdate Adobe Photoshop to version 22.5.7 or later for the 22.x branch, or version 23.3 or later for the 23.x branch. Avoid opening untrusted or unexpected image files.

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:<= 22.5.6>= 23.0.0, <= 23.2.2

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.0/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
    Check for Photoshop.exe on Windows (typically in C:\Program Files\Adobe\Adobe Photoshop [version]\) or Adobe Photoshop.app on macOS (in /Applications/)
    Affected if Adobe Photoshop exists on the system
  2. Retrieve the installed Photoshop version number
    On Windows: Right-click Photoshop.exe, select Properties, view the File Version on the Details tab. On macOS: Right-click Adobe Photoshop.app, select Get Info, view the Version. Or launch Photoshop and go to Help > About Photoshop.
    Affected if Unable to determine the version number or Photoshop is not installed
  3. Compare version against CVE-2022-28275 affected ranges
    Match your installed version against: 22.5.6 or lower; OR 23.0.0 through 23.2.2. Any version in these ranges is vulnerable.
    Affected if Installed version is <= 22.5.6 OR (installed version >= 23.0.0 AND installed version <= 23.2.2)
  4. Confirm the vulnerability trigger condition
    This CVE is triggered when opening a specially crafted malicious image file. Check whether the user or environment opens untrusted or unexpected image files in Photoshop.
    Affected if Users open untrusted or unexpected image files in Adobe Photoshop

You are affected if Adobe Photoshop is installed with version 22.5.6 or lower, or version 23.0.0 through 23.2.2, and users open untrusted image 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 a release after 23.2.2
Interim mitigation

Update Adobe Photoshop to version 22.5.7 or later for the 22.x branch, or version 23.3 or later for the 23.x branch. Avoid opening untrusted or unexpected image files.

Recommended fix Moderate confidence

Update to Photoshop 22.5.7 or later (22.x line), or 23.3.0 or later (23.x line), or the latest available release

  1. 1. Close Adobe Photoshop if it is currently running
  2. 2. Open Adobe Creative Cloud desktop application or navigate to https://creativecloud.adobe.com
  3. 3. Locate Adobe Photoshop in your installed applications
  4. 4. Click on the update option to install the latest version, or manually download the installer from Adobe's official website
  5. 5. Ensure you update to version 22.5.7 or later for the 22.x product line, or version 23.3.0 or later for the 23.x product line
  6. 6. After installation, verify the version by opening Photoshop and going to Help > About Photoshop
  7. 7. Do not open any untrusted or suspicious image files until the update is applied
Caveat Minor release updates typically preserve compatibility with existing files and scripts; review Adobe's release notes for any behavior changes

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

Fix this in Photoshop Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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