# CVE-2026-53777: Perry < 0.5.1159 Path Traversal via ArtifactReady WebSocket

> A malicious build server can exploit path traversal in Perry to overwrite sensitive files or expose local data via unsanitized WebSocket message fields.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Jun 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-x55v-q459-68ch

## What is CVE-2026-53777?

CVE-2026-53777 is a high-severity path traversal vulnerability in PerryTS perry, published on 11 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Perry before 0.5.1159 contains a path traversal vulnerability that allows a malicious build server to write arbitrary content to any location writable by the running process by supplying unsanitized path components in the artifact_name field of ArtifactReady WebSocket messages. Attackers controlling the server URL can deliver traversal payloads through the artifact_name or download_path fields, causing the client to overwrite sensitive files or expose arbitrary local files to an attacker-accessible location.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-53777?


## How do I fix CVE-2026-53777?

No fix has been published for CVE-2026-53777 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-53777 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-53777 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53777 and fix it if it is affected.

What it is: CVE-2026-53777 is a high-severity path traversal vulnerability in PerryTS perry, published on 11 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-53777 exists.

Affected product: PerryTS perry. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-53777/ (Markdown: https://insights.sbomify.com/CVE-2026-53777/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53777
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53777
- OSV: https://osv.dev/vulnerability/CVE-2026-53777

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-53777/
Summaries are generated and may contain mistakes; the official description above is the record.