Photoshop CcApplication · Adobe

CVE-2019-7969

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 · moderate confidence

Adobe Photoshop CC versions 19.1.8 and earlier and 20.0.5 and earlier contain a type confusion vulnerability. This flaw allows an attacker to manipulate object type handling during processing, potentially causing the application to misinterpret data structures and execute arbitrary code in the context of the current user.

MitigationUpgrade Adobe Photoshop CC to version 19.1.9 or later for the 19.x branch, or version 20.0.6 or later 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. Verify Photoshop CC is installed
    Check for Adobe Photoshop CC installation directory (commonly C:\Program Files\Adobe\Adobe Photoshop CC 2019 or C:\Program Files\Adobe\Adobe Photoshop CC 2020) or search for Photoshop.exe in Program Files
    Affected if Photoshop CC is not installed on the system
  2. Determine installed Photoshop version
    Open Photoshop, go to Help > About Photoshop, or right-click Photoshop.exe and select Properties > Details to view the version number
    Affected if The displayed version falls within <= 19.1.8 or >= 20.0.0 and <= 20.0.5
  3. Cross-check version with release history
    Compare the installed version number to the affected ranges: 19.1.8 and earlier, or 20.0.5 and earlier. Versions 19.1.9+ and 20.0.6+ are fixed.
    Affected if Installed version is 19.1.8 or lower, OR between 20.0.0 and 20.0.5 inclusive
  4. Confirm branch and exact version
    Identify whether the installation is the 19.x branch (2019) or 20.x branch (2020) by the version number's first digit
    Affected if Running any of the affected versions in either branch

If Photoshop CC versions 19.1.8 or earlier, or 20.0.5 or earlier are installed, the environment is vulnerable to this type confusion flaw.

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

Upgrade Adobe Photoshop CC to version 19.1.9 or later for the 19.x branch, or version 20.0.6 or later for the 20.x branch.

Recommended fix Moderate confidence

Photoshop CC 19.1.9 or later (19.x branch); or Photoshop CC 20.0.6 or later (20.x branch)

  1. Download Adobe Photoshop CC version 19.1.9 or later from the official Adobe website (helpx.adobe.com)
  2. Alternatively, download Photoshop CC version 20.0.6 or later
  3. Ensure you backup your existing work and preferences before upgrading
  4. Run the installer with administrator privileges
  5. Follow the on-screen installation prompts
  6. Restart your computer after installation to ensure all components are properly initialized
  7. Verify the installed version by opening Photoshop and checking Help > About Photoshop
Caveat Minimal risk - point releases typically include backward-compatible changes; however, complex custom brushes/actions should be backed up before upgrading

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-7969 — 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-7969 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