GHSA-22jr-vc7j-g762 is a critical-severity (CVSS 9.8) CWE-754 vulnerability in psd-tools. A fix is available for psd-tools — see the affected versions and patch details below.
Potential buffer overflow in psd-tools
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-22jr-vc7j-g762 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 376,715 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
psd-toolsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Impact
An issue was discovered in psd-tools before 1.9.4. The Cython implementation of RLE decoding did not check for malformed PSD input data during decoding to the PIL.Image or NumPy format, leading to a Buffer Overflow.
Patches
Users of psd-tools version v1.8.37 to v1.9.3 should upgrade to v1.9.4.
Workarounds
Without Cython present on installation, buffer overflow does not occur but IndexError will be thrown. However, already installed psd-tools with Cython extention should be upgraded.
References
https://github.com/psd-tools/psd-tools/pull/198
For more information
If you have any questions or comments about this advisory:
- Open an issue in psd-tools
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | psd-tools | ≥ 1.8.37&&< 1.9.4 | 1.9.4pip install --upgrade 'psd-tools==1.9.4' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for psd-tools, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update psd-tools to 1.9.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-22jr-vc7j-g762 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-22jr-vc7j-g762 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-22jr-vc7j-g762. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-22jr-vc7j-g762 in your dependencies?
O3 Security finds GHSA-22jr-vc7j-g762 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.