psd-tools is a Python package for working with Adobe Photoshop PSD files. Prior to version 1.12.2, when a PSD file contains malformed RLE-compressed image data (e.g. a literal run that extends past the expected row size), decode_rle() raises ValueError which propagated all the way to the user, crashing psd.composite() and psd-tools export. decompress() already had a fallback that replaces failed channels with black pixels when result is None, but it never triggered because the ValueError from decode_rle() was not caught. The fix in version 1.12.2 wraps the decode_rle() call in a try/except so the existing fallback handles the error gracefully.
CVE-2026-27809
CRITICALNVD 9.19.1
EchelonGraph scoreLOW confidence
This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: nvd
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.1
- EG Score
- 9.1(low)
- EG Risk
- 45(Track)EG Risk 45/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity91% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 34%
- KEV
- Not listed
Published
February 26, 2026
Last Modified
June 17, 2026
Advisory Details (3)
Auto-updated Jul 27, 2026Patch available. Sources: github_commit, github_release, github.
github Patch Available
Compression module: unguarded zlib decompression, missing dimension validation, and minor hardening gaps · Advisory · psd-tools/psd-tools · GitHub
https://github.com/psd-tools/psd-tools/security/advisories/GHSA-24p2-j2jr-386wgithub_release Patch Available
Release v1.12.2
Patch available: psd-tools/psd-tools v1.12.2
https://github.com/psd-tools/psd-tools/releases/tag/v1.12.2github_commit Patch Available
commit 6c0a78f195b5 (psd-tools/psd-tools)
Patch available: psd-tools/psd-tools v1.12.2 (contains commit 6c0a78f195b5)
https://github.com/psd-tools/psd-tools/commit/6c0a78f195b5942757886a1863793fd5946c1fb1Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| psd-tools | 0.1.1 ... 1.9.9 (105 versions) | 1.12.2 | — |
Weakness Classification(6)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-27 13:34 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-190 · CWE-704 · CWE-755
Frequently asked(5)
What is CVE-2026-27809?
CVE-2026-27809 is a critical vulnerability published on February 26, 2026. psd-tools is a Python package for working with Adobe Photoshop PSD files. Prior to version 1.12.2, when a PSD file contains malformed RLE-compressed image data (e.g. a literal run that extends past the expected row size), decoderle() raises ValueError which propagated all the way to the user,…
When was CVE-2026-27809 disclosed?
CVE-2026-27809 was first published in the National Vulnerability Database on February 26, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-27809 actively exploited?
CVE-2026-27809 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 66.4% of all scored CVEs.
What is the CVSS score of CVE-2026-27809?
CVE-2026-27809 has a CVSS v3 base score of 9.1 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-27809?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-27809, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-27809
Is Your Infrastructure Affected by CVE-2026-27809?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.