GHSA-2rmg-vrx8-9j2f: psd-tools vulnerable to arbitrary file write via smart-object filename
psd-tools versions prior to 1.17.1 contain vulnerabilities in the SmartObject API that allow an attacker to write arbitrary files outside the intended output directory via unsanitized smart-object filenames. Additionally, an attacker can read arbitrary files from the filesystem when processing external-kind smart objects, potentially exfiltrating their contents. Both issues arise from lack of validation on file paths derived from untrusted PSD files. These vulnerabilities are fixed in version 1.17.1.
AI Analysis
Technical Summary
In psd-tools versions up to 1.17.0, the SmartObject.save() method writes embedded smart objects to file paths taken directly from the PSD file without sanitization, enabling arbitrary file write through path traversal (e.g., using '../'). The filename property is attacker-controlled and unsanitized, allowing writes outside the intended directory. Additionally, SmartObject.open() for external-kind smart objects uses an attacker-controlled fullPath descriptor without directory constraints, allowing arbitrary file reads. These vulnerabilities enable an attacker to write arbitrary bytes to arbitrary paths and read arbitrary files, potentially exfiltrating sensitive data. Both issues are fixed in version 1.17.1.
Potential Impact
An attacker who can supply or manipulate PSD files processed by psd-tools up to version 1.17.0 can cause the software to write arbitrary data to arbitrary filesystem locations, potentially overwriting critical files. They can also read arbitrary files from the filesystem and write their contents to an output directory, enabling data exfiltration. This can lead to unauthorized file modification and disclosure.
Mitigation Recommendations
Upgrade psd-tools to version 1.17.1 or later, where these vulnerabilities are fixed. The vendor advisory confirms that versions prior to 1.17.1 are affected and that the issues are resolved in 1.17.1. No other mitigations are specified.
GHSA-2rmg-vrx8-9j2f: psd-tools vulnerable to arbitrary file write via smart-object filename
Description
psd-tools versions prior to 1.17.1 contain vulnerabilities in the SmartObject API that allow an attacker to write arbitrary files outside the intended output directory via unsanitized smart-object filenames. Additionally, an attacker can read arbitrary files from the filesystem when processing external-kind smart objects, potentially exfiltrating their contents. Both issues arise from lack of validation on file paths derived from untrusted PSD files. These vulnerabilities are fixed in version 1.17.1.
CVSS v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In psd-tools versions up to 1.17.0, the SmartObject.save() method writes embedded smart objects to file paths taken directly from the PSD file without sanitization, enabling arbitrary file write through path traversal (e.g., using '../'). The filename property is attacker-controlled and unsanitized, allowing writes outside the intended directory. Additionally, SmartObject.open() for external-kind smart objects uses an attacker-controlled fullPath descriptor without directory constraints, allowing arbitrary file reads. These vulnerabilities enable an attacker to write arbitrary bytes to arbitrary paths and read arbitrary files, potentially exfiltrating sensitive data. Both issues are fixed in version 1.17.1.
Potential Impact
An attacker who can supply or manipulate PSD files processed by psd-tools up to version 1.17.0 can cause the software to write arbitrary data to arbitrary filesystem locations, potentially overwriting critical files. They can also read arbitrary files from the filesystem and write their contents to an output directory, enabling data exfiltration. This can lead to unauthorized file modification and disclosure.
Mitigation Recommendations
Upgrade psd-tools to version 1.17.1 or later, where these vulnerabilities are fixed. The vendor advisory confirms that versions prior to 1.17.1 are affected and that the issues are resolved in 1.17.1. No other mitigations are specified.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-2rmg-vrx8-9j2f
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-49836"]
- Ecosystems
- ["PyPI"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 4.0
Threat ID: 6a50ba3c68715ace4357db17
Added to database: 07/10/2026, 09:24:12 UTC
Last enriched: 07/10/2026, 09:33:13 UTC
Last updated: 07/10/2026, 13:51:16 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.