PhotoshopApplication · Adobe

CVE-2021-43018

HIGH · 7.8 CVSS v3.1 Published 2023-09-07
Fix available
A fix is available. Upgrade to 22.5.4 / 23.0.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 23.0.2 and 22.5.4 (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 JPG 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

An out-of-bounds write vulnerability exists in Adobe Photoshop when parsing maliciously crafted JPG files. By opening a specially crafted JPG file, an attacker can trigger memory corruption that leads to arbitrary code execution in the context of the current user.

MitigationUpdate Adobe Photoshop to a version beyond 23.0.2 or 22.5.4, and exercise caution when opening JPG files from untrusted sources.

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.0, < 22.5.4>= 23.0.0, < 23.0.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.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. Determine installed Photoshop version
    Open Photoshop, then go to Help > About Photoshop. The version number is displayed in the dialog that opens.
    Affected if The version shown is 22.0 through 22.5.3, or 23.0.0 through 23.0.1.
  2. Alternative version check via file properties
    In the Adobe Photoshop installation folder, right-click Photoshop.exe, select Properties, and view the Details tab to see the Product Version.
    Affected if The version listed falls within 22.0.x (before 22.5.4) or 23.0.0-23.0.1.
  3. Confirm the attack surface exists
    Verify that the Photoshop installation includes JPG file handling capability (standard in all typical Photoshop installations). This is the default; no special modules are required.
    Affected if Photoshop can open and parse JPG files, which is the default behavior.

A user is affected if they are running Photoshop versions 22.0 through 22.5.3 or 23.0.0 through 23.0.1 and have opened or intend to open untrusted JPG 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 22.5.4 / 23.0.2 or later
Fixed in 22.5.423.0.2
Interim mitigation

Update Adobe Photoshop to a version beyond 23.0.2 or 22.5.4, and exercise caution when opening JPG files from untrusted sources.

Recommended fix High confidence

Photoshop 22.5.4 or later for 22.x branch; Photoshop 23.0.2 or later for 23.x branch

  1. 1. Launch Adobe Photoshop
  2. 2. Go to Help > Check for Updates to open the Adobe Creative Cloud desktop application
  3. 3. In the Creative Cloud app, locate Photoshop in the list of installed apps
  4. 4. Click Update to install the latest version
  5. 5. Alternatively, manually download the fixed version from helpx.adobe.com: Photoshop 22.5.4 for the 22.x branch or Photoshop 23.0.2 (or later) for the 23.x branch
  6. 6. Restart Photoshop after the update completes
  7. 7. Verify the installed version by going to Help > About Photoshop
Caveat Minimal risk; Adobe patches rarely introduce breaking changes but review release notes for any plugin or workflow adjustments

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

Fix this in Photoshop Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-43018 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-43018 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