CVE-2023-26370
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 versions 23.5.5 (and earlier) and 24.7 (and earlier) are affected by an Access of Uninitialized Pointer vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.
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 versions 23.5.5 and earlier and 24.7 and earlier contain an Access of Uninitialized Pointer vulnerability that can be exploited to achieve arbitrary code execution. The attack vector requires a victim to open a maliciously crafted file, with the code executing in the context of the current user session.
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<= 23.5.5< 24.7.1< 25.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 Photoshop versionOpen Photoshop and go to Help > About Photoshop, or check the version in the application title bar. Alternatively, on Windows check the file properties of the executable (typically in C:\Program Files\Adobe\Adobe Photoshop 20XX\Photoshop.exe), or on macOS use Get Info on the Photoshop.app.Affected if The displayed version falls within the affected ranges (23.5.5 or earlier for 2022, 24.7.0 or earlier for 2023, or 24.x versions before 24.7.1, or 25.0 or earlier for 2024).
-
Determine Photoshop release year (channel)The version number format indicates the release year: versions 23.x correspond to Photoshop 2022, 24.x to Photoshop 2023, and 25.x to Photoshop 2024. Check the About dialog or your installation documentation to confirm which release year you are running.Affected if You are running Photoshop 2022, 2023, or 2024 release channels.
-
Verify exact version against thresholdsCompare your installed three-part version number (major.minor.patch) to the affected thresholds: 23.5.5 (max safe for 2022), 24.7.0 (vulnerable in 2023), 24.7.1 (minimum fixed for 2023), or 25.0 (vulnerable for 2024).Affected if Your version is 23.5.5 or lower, or is 24.7.0 or lower, or is any version from 24.7.1 through 24.x below 24.7.1 (which is not possible as 24.7.1 is the fix), or is 25.0 or any 25.x version below 25.0.
-
Confirm file association handlingThis vulnerability is triggered when opening a maliciously crafted file. Check whether your system is configured to automatically open files in Photoshop or if you frequently open files from untrusted or unknown sources.Affected if You regularly open PSD or other image files from untrusted or unknown sources using Photoshop, which would enable the exploit to trigger.
You are affected if you are running any version of Photoshop 2022 at 23.5.5 or earlier, any version of Photoshop 2023 at 24.7.0 or earlier, or any version of Photoshop 2024 at 25.0 or earlier, and you open malicious files with the application.
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 · scoped24.7.125.0
Upgrade Adobe Photoshop to the latest version (23.5.6 or later for the 23.x branch, 24.7.1 or later for the 24.x branch) and exercise caution when opening files from untrusted sources.
Photoshop 2022: update to 23.5.6 or later | Photoshop 2023: update to 24.7.1 or later | Photoshop 2024: update to 25.0 or later
- Close Photoshop completely before updating
- Open Adobe Creative Cloud desktop application
- Navigate to the Apps tab
- Find Adobe Photoshop in your installed apps list
- Click the Update button next to Photoshop
- Wait for the update to download and install
- Restart your computer after installation completes
- Launch Photoshop and verify the version number matches the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.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 $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-26370 — 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-2023-26370 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