PhotoshopApplication · Adobe

CVE-2021-36065

HIGH · 7.8 CVSS v3.1 Published 2021-09-01
Fix available
A fix is available. Upgrade to after 22.4.3 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 21.2.10 (and earlier) and 22.4.3 (and earlier) are affected by a heap-based buffer overflow 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 versions 21.2.10 and earlier, and 22.4.3 and earlier contain a heap-based buffer overflow vulnerability that can be triggered by opening a specially crafted malicious file, leading to arbitrary code execution in the context of the current user.

MitigationUpdate Adobe Photoshop to version 22.5 or later to patch the vulnerability. Avoid opening untrusted or unexpected image 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:>= 21.2.0, <= 21.2.10>= 22.4.0, <= 22.4.3

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, go to Help > About Photoshop, or check the file version of Photoshop.exe in the installation directory (right-click > Properties > Details). On Windows, also check the registry key HKLM\SOFTWARE\Adobe\Photoshop\InstallVersion.
    Affected if Version falls within 21.2.0-21.2.10 or 22.4.0-22.4.3
  2. Confirm Photoshop edition (2021 vs 2022)
    The version number indicates the release year: versions 21.x correspond to Photoshop 2021, and versions 22.x correspond to Photoshop 2022. Check the version displayed in Help > About Photoshop.
    Affected if Edition is 2021 (version 21.x) in range 21.2.0-21.2.10, or 2022 (version 22.x) in range 22.4.0-22.4.3
  3. Identify if untrusted files were opened
    Review recent file access or check if any unexpected or untrusted image files (.psd, .png, .jpg, .tif, or other image formats) were opened in Photoshop around the time of potential compromise.
    Affected if A specially crafted malicious image file was opened in the affected Photoshop version
  4. Check for suspicious behavior
    Review system logs, browser downloads, or email attachments for evidence of recently opened untrusted image files that may have been downloaded from untrusted sources.
    Affected if Unexpected image files from untrusted sources were opened in Photoshop

A user is affected if their installed Photoshop version is 21.2.0 through 21.2.10 or 22.4.0 through 22.4.3 AND they have opened a specially crafted malicious image file.

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 22.4.3
Interim mitigation

Update Adobe Photoshop to version 22.5 or later to patch the vulnerability. Avoid opening untrusted or unexpected image files from untrusted sources.

Recommended fix High confidence

Photoshop 21.2.11 or later for the 21.x line; Photoshop 22.4.4 or later for the 22.x line

  1. Open Adobe Photoshop
  2. Navigate to Help > Check for Updates
  3. Allow Adobe Creative Cloud to check for and install the latest version
  4. Alternatively, download the latest version from the official Adobe website

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

Fix this in Photoshop Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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