CVE-2019-7994
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 · moderate confidenceOut-of-bounds write vulnerability in Adobe Photoshop CC versions 19.1.8 and earlier and 20.0.5 and earlier. Exploitation occurs via specially crafted image files that trigger memory corruption during processing, potentially allowing arbitrary code execution with the privileges of the user running 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<= 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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.
-
Identify installed Adobe Photoshop CC versionOpen Photoshop and go to Help > About Photoshop, or check your system's installed programs list. Note the full version number (e.g., 19.1.8, 20.0.5).Affected if Version is 19.1.8 or earlier, OR between 20.0 and 20.0.5 inclusive
-
Confirm Photoshop version branchDetermine whether you are on the 19.x (CC 2018) or 20.x (CC 2019) release branch by examining the version number's major.minor components.Affected if Running any 19.x version up to 19.1.8, or any 20.x version up to 20.0.5
-
Verify image processing usageCheck if the system or user profile runs Photoshop to open or process image files (JPEG, PNG, TIFF, or other formats). This is the default function of Photoshop.Affected if Photoshop is used to open image files from any source, as exploitation occurs during image file processing
Your environment is affected if Adobe Photoshop CC version is 19.1.8 or earlier, or any version from 20.0 through 20.0.5, and you use Photoshop to open or process image 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.
From vendor dataUpdate Adobe Photoshop CC to a version newer than 20.0.5 or 19.1.8 (whichever branch is in use). If immediate patching is not feasible, exercise caution when opening image files from untrusted sources.
- Consultation2.0 h
- Implementation1.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,944.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7994 — 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-7994 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