CVE-2019-7094
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 19.1.7 and earlier, and 20.0.2 and earlier have a heap corruption 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 confidenceHeap corruption vulnerability in Adobe Photoshop CC allows attackers to corrupt heap memory, potentially leading to arbitrary code execution. The vulnerability affects versions 19.1.7 and earlier (2018 release) and 20.0.2 and earlier (2019 release).
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.7>= 20.0, <= 20.0.2CVSS 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.
-
Check installed Photoshop CC version via registryOpen Windows Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Photoshop\InstallVersion, or check the version in Help > About Photoshop within the applicationAffected if Version is 19.1.7 or lower, or 20.0.2 or lower (but greater than or equal to 20.0)
-
Confirm the specific release yearDetermine if the installation is the 2018 release (version 19.x) or the 2019 release (version 20.x)Affected if The version matches the 2018 release branch at 19.1.7 or below, or the 2019 release branch at 20.0 through 20.0.2
-
Verify Photoshop is actively used or accessibleCheck whether the Photoshop executable (Photoshop.exe) exists on the system and the application is installedAffected if The vulnerable software is installed and available for use
You are affected if Adobe Photoshop CC version 19.1.7 or earlier (2018) or version 20.0 through 20.0.2 (2019) is installed on the system.
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 · scopedOrganizations should identify and upgrade affected Photoshop installations to patched versions. Until patches are applied, restrict usage of untrusted image files and consider network isolation for vulnerable systems.
Apply Adobe's security patch (refer to helpx.adobe.com security bulletin for exact version)
- Navigate to Adobe's official security bulletin or helpx.adobe.com for Photoshop CC security updates
- Locate the security update for CVE-2019-7094
- Download and install the security patch from Adobe's official sources
- Alternatively, update Photoshop CC through the Creative Cloud desktop application by checking for updates
- Verify the installed version matches or exceeds the patched version after installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7094 — 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-7094 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