Photoshop CcApplication · Adobe

CVE-2019-7975

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 a type confusion 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 a type confusion vulnerability that allows attackers to execute arbitrary code by exploiting improper type handling in the software.

MitigationUpdate Adobe Photoshop CC to a version newer than 19.1.8 or 20.0.5, or apply the vendor-supplied patch. Prioritize this critical update given the CVSS 9.8 severity and arbitrary code execution capability.

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 installed Photoshop version on Windows
    Open Registry Editor and navigate to HKLM\SOFTWARE\Adobe\Photoshop\Version, or check the version property of the Photoshop.exe file in the installation directory
    Affected if The Version value is 19.1.8 or lower, or falls between 20.0.0 and 20.0.5 inclusive
  2. Check installed Photoshop version on macOS
    Right-click Photoshop in /Applications, select Get Info, or run: defaults read /Applications/Adobe\ Photoshop\ CC\ 20\ 20.0/Adobe\ Photoshop\ CC\ 20.app/Contents/Info CFBundleShortVersionString
    Affected if The version string is 19.1.8 or lower, or falls between 20.0.0 and 20.0.5 inclusive
  3. Check version via Photoshop Help menu
    Open Photoshop, go to Help > About Photoshop. The version number appears in the splash dialog
    Affected if The displayed version is 19.1.8 or earlier, or 20.0.5 or earlier
  4. Verify version matches affected ranges
    Compare your installed version number against the two affected ranges: versions 19.1.8 and earlier, OR versions 20.0 through 20.0.5
    Affected if Your installed version falls within either of these ranges

You are affected if your installed Adobe Photoshop CC version is 19.1.8 or lower, or between 20.0 and 20.0.5 inclusive.

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 version newer than 19.1.8 or 20.0.5, or apply the vendor-supplied patch. Prioritize this critical update given the CVSS 9.8 severity and arbitrary code execution capability.

Recommended fix High confidence

Photoshop CC 19.1.9 (for 19.x branch) or 20.0.6+ (for 20.x branch)

  1. Open Adobe Creative Cloud desktop application
  2. Navigate to the Apps tab
  3. Find Adobe Photoshop CC in your installed apps
  4. Click on the three-dot menu next to Photoshop
  5. Select 'Update' to install the latest version
  6. Alternatively, manually download the update from helpx.adobe.com Photoshop security bulletin
  7. Restart Photoshop after the update completes
  8. Verify the version by going to Help > About Photoshop to confirm version 19.1.9 or 20.0.6+
Caveat Standard security update; minimal risk of breaking changes; backup custom presets and workspaces before updating as precaution

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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