Security readout for executives and security teams
Plain-English summary
CVE-2026-27809 affects psd-tools, a Python library used to process Photoshop PSD files. Before 1.12.2, certain malformed compressed PSD image data can crash composition or export workflows instead of being handled gracefully. Business risk is mainly disruption to services or automation that process PSD files, especially if users can upload or submit files.
Executive priority
Treat as a medium-priority availability issue. Patch promptly in file-processing services exposed to customers or partners. Lower urgency applies to internal-only tools processing trusted PSDs, but upgrading remains the cleanest risk reduction.
Technical view
In psd-tools versions before 1.12.2, malformed RLE-compressed image data can cause decode_rle() to raise ValueError. That exception was not caught, so psd.composite() and export operations could crash. Version 1.12.2 wraps decode_rle() with exception handling so the existing fallback can replace failed channels with black pixels.
Likely exposure
Exposure is likely in applications, workers, or media pipelines using psd-tools below 1.12.2 to process PSD files. Risk increases when PSD files come from untrusted users, external partners, or automated ingestion channels.
Exploitation context
The source bundle does not indicate active exploitation, and the CVE is not marked as CISA KEV. The issue appears triggerable through malformed PSD content processed by vulnerable psd-tools code. No exploit details are needed to understand exposure.
Researcher notes
The public description centers on uncaught ValueError handling in RLE decompression. The title references broader decompression and validation hardening gaps, but provided details identify the concrete fix as catching decode_rle() failures and using the existing fallback path.
Mitigation direction
- Upgrade psd-tools to version 1.12.2 or later.
- Prioritize systems processing untrusted or user-supplied PSD files.
- Restrict PSD ingestion where upgrades cannot be completed promptly.
- Check the GitHub advisory and release notes for current vendor guidance.
Validation and detection
- Inventory Python environments for psd-tools usage.
- Confirm installed psd-tools versions are 1.12.2 or later.
- Review upload, conversion, and export services that process PSD files.
- Monitor logs for PSD processing crashes or repeated ValueError failures.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-190: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-409: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-617: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-704: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-755: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-789: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.8 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N/E:U
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N/E:U——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
6.8MediumVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N/E:U
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/psd-tools/psd-tools/security/advisories/GHSA-24p2-j2jr-386wCVE reference · x_refsource_CONFIRM
- https://github.com/psd-tools/psd-tools/commit/6c0a78f195b5942757886a1863793fd5946c1fb1CVE reference · x_refsource_MISC
- https://github.com/psd-tools/psd-tools/releases/tag/v1.12.2CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
