Photoshop CcApplication · Adobe

CVE-2019-7998

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

Adobe Photoshop CC versions 19.1.8 and earlier and 20.0.5 and earlier contain an out-of-bounds write vulnerability, a memory corruption flaw that allows writing beyond allocated buffer boundaries. Successful exploitation enables an attacker to execute arbitrary code on the targeted system, potentially achieving full system compromise.

MitigationUpdate Adobe Photoshop CC to version 19.1.9 or later (for the 19.x branch) and version 20.0.6 or later (for the 20.x branch). Until patched, exercise caution when opening untrusted image files in Photoshop.

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. Identify installed Photoshop CC version
    Open Photoshop, go to Help > About Photoshop, or on Windows right-click Photoshop.exe in Program Files > Properties > Details tab, or on Mac use Get Info on Adobe Photoshop CC.app in /Applications
    Affected if Version number displayed is 19.1.8 or lower, OR between 20.0 and 20.0.5 inclusive
  2. Verify Photoshop CC edition
    Confirm the installation is Adobe Photoshop CC (not Photoshop Elements or other variants) - check the application name in the Start Menu, Applications folder, or Help > About Photoshop window
    Affected if The installed product is Adobe Photoshop CC and version falls in affected ranges from step 1
  3. Confirm the vulnerable component is present
    The vulnerability exists in Photoshop's image file parsing engine. Verify Photoshop can open image files (JPEG, PNG, TIFF, or other formats) by checking that the standard file open dialog shows supported image types and the application has not had its image processing modules removed
    Affected if Photoshop can open and process image files - this is the component that processes the malformed images which trigger the out-of-bounds write

A user is affected if Adobe Photoshop CC version is 19.1.8 or earlier, or any version from 20.0 through 20.0.5, and the application processes 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 20.0.5
Interim mitigation

Update Adobe Photoshop CC to version 19.1.9 or later (for the 19.x branch) and version 20.0.6 or later (for the 20.x branch). Until patched, exercise caution when opening untrusted image files in Photoshop.

Recommended fix Moderate confidence

Photoshop CC 19.1.9 or later / Photoshop CC 20.0.6 or later

  1. Navigate to Adobe's official security bulletin for this vulnerability on helpx.adobe.com to obtain the specific fixed version and download link
  2. Open Adobe Creative Cloud Desktop Application
  3. Navigate to the Apps tab and locate Photoshop CC
  4. If an update is available, click Update to install the fixed version
  5. Alternatively, manually download the fixed Photoshop CC version (19.1.9 or 20.0.6 and later) from Adobe's website
Caveat Standard Photoshop update - review Adobe's release notes for any feature changes or deprecations in the new version

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

Fix this in Photoshop Cc Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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