CVE-2019-8001
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 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 confidenceAdobe Photoshop CC versions 19.1.8 and earlier and 20.0.5 and earlier contain an out-of-bounds write vulnerability that can be exploited to achieve arbitrary code execution. The vulnerability is remotely exploitable with low attack complexity and no authentication required, making it highly dangerous.
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.
-
Verify Photoshop CC is installedCheck for Adobe Photoshop CC installation on the system. On Windows, look in Program Files or Program Files (x86) for an Adobe Photoshop CC folder. On macOS, check /Applications for Adobe Photoshop CC applications.Affected if Adobe Photoshop CC is installed on the system
-
Determine installed Photoshop versionOpen Photoshop and go to Help > About Photoshop to view the exact version number. On Windows, you can also check the registry at HKLM\SOFTWARE\Adobe\Photoshop\ (or the WOW6432Node path for 64-bit) for the Version or InstanceID value.Affected if Version displayed is 19.1.8 or earlier, or 20.0.5 or earlier
-
Compare against affected version rangesIf using the 19.x branch, check if version is 19.1.8 or lower. If using the 20.x branch, check if version is 20.0.5 or lower. Note that versions 19.1.9 and above (19.x branch) and 20.0.6 and above (20.x branch) are patched.Affected if Installed version falls within the 19.1.8 and earlier range OR the 20.0.5 and earlier range
The system is affected if Adobe Photoshop CC is installed with version 19.1.8 or earlier, or version 20.0.5 or earlier.
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 · scopedUpgrade 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) to address the out-of-bounds write vulnerability.
Photoshop CC 19.1.9 or later (19.x line); Photoshop CC 20.0.6 or later (20.x line)
- Navigate to the Adobe Creative Cloud desktop application or go to helpx.adobe.com/pshop/
- Open Adobe Creative Cloud and locate Photoshop in the Apps tab
- Check for available updates - the update should show as Photoshop CC 19.1.9 for the 19.x line and Photoshop CC 20.0.6 for the 20.x line
- Click Update to download and install the fixed version
- Alternatively, download the update directly from helpx.adobe.com/pshop/ by selecting your version and checking for security updates
- After installation, verify the version by going to Help > About Photoshop and confirm it shows 19.1.9 or 20.0.6 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-8001 — 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-8001 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