CVE-2019-7996
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 read vulnerability. Successful exploitation could lead to memory leak.
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 confidenceAdobe Photoshop CC versions 19.1.8 and earlier and 20.0.5 and earlier contain an out-of-bounds read vulnerability. Successful exploitation allows an attacker to read memory beyond allocated buffers, potentially leading to information disclosure through memory leak. The high CVSS score (8.8) indicates significant potential impact if exploited.
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.
-
Verify Adobe Photoshop CC is installedOpen Photoshop and go to Help > About Photoshop, or check Programs and Features (Windows) / Applications folder (Mac) for Adobe Photoshop CCAffected if Photoshop CC is not present on the system, the vulnerability does not apply
-
Identify the installed Photoshop version numberIn Photoshop: Help > About Photoshop displays the version (e.g., 19.1.8 or 20.0.5). On Windows, also check the version in Programs and Features. On macOS, right-click Photoshop.app > Get Info shows the version.Affected if The exact version number cannot be determined, assume potentially affected
-
Compare version against affected 19.x rangeIf the version starts with 19 (e.g., 19.1.x), check if it is 19.1.8 or any earlier 19.x releaseAffected if Version is 19.1.8 or earlier (19.1.0 through 19.1.8)
-
Compare version against affected 20.x rangeIf the version starts with 20, check if it is 20.0.5 or any earlier 20.0.x releaseAffected if Version is 20.0.5 or earlier (20.0.0 through 20.0.5)
-
Confirm major version is CC (not other editions)Ensure the installed product is Photoshop CC (Creative Cloud), not Photoshop CS6 or Elements. Check the product name in Help > About Photoshop which shows 'Adobe Photoshop CC'Affected if The product is Photoshop CC (Creative Cloud) and version falls within affected ranges
User is affected if Adobe Photoshop CC is installed and the version is 19.1.8 or earlier, or 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.
From vendor dataUpdate Adobe Photoshop CC to version 19.1.9 or later, or version 20.0.6 or later. Organizations should deploy the vendor patch across all affected systems and verify successful installation.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7996 — 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-7996 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