CVE-2022-28270
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 · uneditedAdobe 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 SVG 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 versions 22.5.6 and earlier and 23.2.2 and earlier contain an out-of-bounds write vulnerability when parsing malicious SVG files. An attacker can craft a specially designed SVG file that, when opened by a victim, triggers the vulnerability and allows arbitrary code execution in the context of the current user's privileges.
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<= 22.5.6>= 23.0, <= 23.2.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Adobe Photoshop is installedCheck for Photoshop executable (Photoshop.exe) in typical installation paths such as C:\Program Files\Adobe\Adobe Photoshop [version] on Windows or /Applications/Adobe Photoshop [version] on macOSAffected if Photoshop is present on the system
-
Determine the installed Photoshop version numberRight-click Photoshop.exe, select Properties, then Details to view the File Version, or open Photoshop and go to Help > About PhotoshopAffected if Cannot determine version from the executable
-
Compare installed version against affected rangesMatch the discovered version to the vulnerable ranges: 22.x versions 22.5.6 and earlier, or 23.x versions 23.0 through 23.2.2Affected if Installed version is 22.5.6 or earlier, or falls between 23.0 and 23.2.2 inclusive
-
Confirm SVG file handling is enabledAttempt to open an SVG file in Photoshop, or check if .svg is associated as a file type Photoshop can open (File > Open, then look for SVG in the file type dropdown)Affected if SVG files can be opened in Photoshop and the version is in the affected range
User is affected if Photoshop is installed with a version in the 22.5.6 or earlier range, or in the 23.0 to 23.2.2 range, and the application can open SVG files.
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 · scopedUpgrade Adobe Photoshop to a patched version (23.3 or later for the 23.x branch, 22.5.7 or later for the 22.x branch) to remediate this vulnerability. Until patched, avoid opening untrusted SVG files in Photoshop.
Upgrade to Photoshop 22.5.7 or later (for 22.x branch) OR Photoshop 23.2.3 or later (for 23.x branch), or migrate to the latest available version
- 1. Close any running instances of Adobe Photoshop
- 2. Back up your current Photoshop settings and presets (optional but recommended)
- 3. Open Adobe Creative Cloud desktop application
- 4. Navigate to the Apps tab
- 5. Find Adobe Photoshop in your installed apps
- 6. Click on the More Actions menu (three dots) next to Photoshop
- 7. Select 'Update' to install the latest available version
- 8. Wait for the update to download and install completely
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28270 — 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-2022-28270 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