Photoshop CcApplication · Adobe

CVE-2018-12810

CRITICAL · 9.8 CVSS v3.0 Published 2018-08-29
Fix available
A fix is available. Upgrade to after 19.1.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Adobe Photoshop CC 2018 before 19.1.6 and Photoshop CC 2017 before 18.1.6 have a memory corruption vulnerability. Successful exploitation could lead to remote 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 confidence

This is a memory corruption vulnerability in Adobe Photoshop CC 2017 and 2018 versions prior to 18.1.6 and 19.1.6 respectively. The vulnerability allows attackers to exploit improper memory handling to achieve remote code execution, likely through specially crafted image files processed by the application.

MitigationUpgrade Adobe Photoshop CC to version 18.1.6 or later for the 2017 release, or 19.1.6 or later for the 2018 release to remediate this vulnerability.

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
Photoshop CcApplication
Affected:>= 19.0.0, <= 19.1.5>= 18.0.0, <= 18.1.5

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate Adobe Photoshop CC installation
    Check common installation directories: C:\Program Files\Adobe\Adobe Photoshop CC 2017 or C:\Program Files\Adobe\Adobe Photoshop CC 2018 on Windows; /Applications/Adobe Photoshop CC 2017.app or /Applications/Adobe Photoshop CC 2018.app on macOS
    Affected if Adobe Photoshop CC 2017 or CC 2018 is installed on the system
  2. Identify the installed Photoshop version number
    On Windows: Right-click the Photoshop shortcut, select Properties, and check the Details tab for the version. On macOS: Right-click the app, select Get Info, and view the Version field. Alternatively, open Photoshop and go to Help > About Photoshop to display the version dialog.
    Affected if The version displayed is 18.x (2017) or 19.x (2018)
  3. Compare version against vulnerable ranges
    Check if the installed version falls within: 18.0.0 through 18.1.5 (CC 2017) OR 19.0.0 through 19.1.5 (CC 2018)
    Affected if The installed version is 18.1.5 or earlier for CC 2017, or 19.1.5 or earlier for CC 2018

The system is affected if Adobe Photoshop CC 2017 version 18.1.5 or earlier, or CC 2018 version 19.1.5 or earlier, is installed and processes untrusted image files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 19.1.5
Interim mitigation

Upgrade Adobe Photoshop CC to version 18.1.6 or later for the 2017 release, or 19.1.6 or later for the 2018 release to remediate this vulnerability.

Recommended fix High confidence

Photoshop CC 2017 version 18.1.6 or later; Photoshop CC 2018 version 19.1.6 or later

  1. Close Adobe Photoshop if it's currently running
  2. Back up any important Photoshop files, projects, and preferences as a precaution
  3. Open the Adobe Creative Cloud desktop application on your system
  4. Navigate to the Apps tab in the Creative Cloud interface
  5. Locate Adobe Photoshop CC in the list of installed applications
  6. If an update is available, click the 'Update' button next to Photoshop CC
  7. Wait for the update to download and install completely
  8. Restart your computer if prompted by the installer
Caveat Point releases typically have minimal breaking changes; back up work before updating as a precaution

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Photoshop Cc Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-12810 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-12810 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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