File write and disclosure via unsanitized artifact paths
Published Jun 11, 2026 · Updated Jun 11, 2026
Path traversal in Perry before 0.5.1159 allows remote attackers controlling a build server to write files through crafted WebSocket fields. The perry publish handler joins an unsanitized ArtifactReady artifact_name to the output path and honors a server-selected download_path as a local source. Exploitation requires a developer or CI runner to publish against the malicious server; it permits overwriting process-writable files or copying readable local files into the output directory.
Summary
What happened
Path traversal in Perry before 0.5.1159 allows remote attackers controlling a build server to write files through crafted WebSocket fields. The perry publish handler joins an unsanitized ArtifactReady artifact_name to the output path and honors a server-selected download_path as a local source. Exploitation requires a developer or CI runner to publish against the malicious server; it permits overwriting process-writable files or copying readable local files into the output directory.
The record
- CVE
- CVE-2026-53777
- Published
- Jun 11, 2026
- Updated
- Jun 11, 2026
- Vendor
- PerryTS
- Product
- Perry
- Classifications
- CWE-22, T1105, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 11, 2026CVE publishedPublication date reported by the CVE source.
- Jun 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.5.1159
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- ArtifactReady malicious WebSocket server proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo