Photoshop CcApplication · Adobe

CVE-2019-7997

CRITICAL · 9.8 CVSS v3.0 Published 2019-08-26
Fix available
A fix is available. Upgrade to after 20.0.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 CC versions 19.1.8 and earlier and 20.0.5 and earlier have an out of bound write vulnerability. Successful exploitation could lead to arbitrary code execution.

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

Out-of-bounds write vulnerability in Adobe Photoshop CC versions 19.1.8 and earlier (19.x branch) and 20.0.5 and earlier (20.x branch). The vulnerability allows writing data beyond allocated memory boundaries, which can be leveraged to achieve arbitrary code execution.

MitigationUpdate Adobe Photoshop CC to a patched version newer than 19.1.8 for the 19.x branch or newer than 20.0.5 for the 20.x branch.

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
Photoshop CcApplication
Affected:<= 19.1.8>= 20.0, <= 20.0.5

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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. Check Photoshop version from within the application
    Open Photoshop, go to Help > About Photoshop (or Photoshop > About Photoshop on Mac). Note the version number displayed in the dialog.
    Affected if The version shown is 19.1.8 or earlier for the 19.x branch, or 20.0.5 or earlier for the 20.x branch.
  2. Check version via Creative Cloud desktop app
    Open the Creative Cloud app, click on the Photoshop card or icon, and view the installed version number listed under the product name.
    Affected if The listed version falls within the affected ranges: 19.1.8 or earlier, or any version from 20.0 through 20.0.5.
  3. Check Windows file version (Windows only)
    Navigate to the Photoshop installation directory (typically C:\Program Files\Adobe\Adobe Photoshop CC 2018 or CC 2019), right-click on Photoshop.exe, select Properties, and view the File version on the Details tab.
    Affected if The file version matches 19.1.8 or lower (19.x branch) or 20.0.5 or lower (20.x branch).
  4. Check macOS application bundle version
    In Finder, locate Adobe Photoshop CC, right-click and select Get Info, or control-click and choose Show Package Contents. Check Contents/Info.plist for CFBundleShortVersionString and CFBundleVersion values.
    Affected if The bundle version string indicates 19.1.8 or earlier, or any version from 20.0 through 20.0.5.

A system is affected if Adobe Photoshop CC is installed with a version in the 19.x branch at 19.1.8 or earlier, or in the 20.x branch at 20.0.5 or earlier.

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

Update Adobe Photoshop CC to a patched version newer than 19.1.8 for the 19.x branch or newer than 20.0.5 for the 20.x branch.

Recommended fix High confidence

Photoshop CC 2018: upgrade to 19.1.9 or later; Photoshop CC 2019: upgrade to 20.1 or later

  1. Upgrade Photoshop CC 2018 (version 19.x) to version 19.1.9 or later
  2. Upgrade Photoshop CC 2019 (version 20.x) to version 20.1 or later
  3. Verify the update was applied successfully by checking Help > About Photoshop

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

Fix this in Photoshop Cc Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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