CVE-2019-7971
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 · uneditedAdobe 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 confidenceAdobe Photoshop CC versions 19.1.8 and earlier (Photoshop CC 2018) and 20.0.5 and earlier (Photoshop CC 2019) contain a type confusion vulnerability that could allow remote attackers to execute arbitrary code on affected systems.
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<= 19.1.8>= 20.0, <= 20.0.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Adobe Photoshop CC installationCheck if Adobe Photoshop CC is installed on the system by looking for the application in the system application list, installation directory, or by querying installed programs.Affected if Adobe Photoshop CC is installed on the system
-
Determine installed Photoshop versionOpen Adobe Photoshop CC and navigate to Help > About Photoshop, or check the application version through the system information or installed programs list. Note the full version number (for example: 19.1.8 or 20.0.5).Affected if The displayed version matches 19.x series at 19.1.8 or earlier, OR 20.x series at 20.0.5 or earlier
-
Identify the specific Photoshop release (2018 or 2019)Cross-reference the major version number: version 19.x corresponds to Photoshop CC 2018, version 20.x corresponds to Photoshop CC 2019.Affected if The installed version is CC 2018 (19.x branch at 19.1.8 or below) or CC 2019 (20.x branch at 20.0.5 or below)
A system is affected if Adobe Photoshop CC 2018 version 19.1.8 or earlier, or CC 2019 version 20.0.5 or earlier is installed and the application is used to open untrusted files.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate Adobe Photoshop CC to the patched versions (19.1.9 or later for CC 2018, 20.0.6 or later for CC 2019) as soon as possible given the critical CVSS score and potential for arbitrary code execution.
Adobe Photoshop CC 19.1.9 or later for version 19.x; Adobe Photoshop CC 20.0.6 or later for version 20.x
- Verify the current Photoshop version by opening Photoshop and navigating to Help > About Photoshop
- Close all Adobe applications before updating
- Open Adobe Creative Cloud desktop application
- Navigate to the Apps section
- Find Adobe Photoshop CC in the list
- Click on Update to install the latest version
- Restart Photoshop after the update completes
- Verify the updated version by checking Help > About Photoshop
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2019-7971 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-7971 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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