# CVE-2026-56815: Path traversal in pwnlift

> An attacker can exploit symlink following in the upload handler to read or modify arbitrary files in privileged deployments.

- **Severity:** High 7.4 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jun 2026
- **Updated:** 2 Jul 2026
- **Also known as:** GHSA-9x6c-xp5w-ch33

## What is CVE-2026-56815?

CVE-2026-56815 is a high-severity path traversal vulnerability in rasta-mouse pwnlift, published on 23 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

pwnlift before d7a9544, in a privileged deployment, contains a symlink following vulnerability in the upload handler in Components/Pages/Home.razor.

Weakness: CWE-61 (UNIX Symbolic Link (Symlink) Following)

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


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

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

## Is CVE-2026-56815 being exploited?

There is no known exploitation of CVE-2026-56815 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-56815 is a high-severity path traversal vulnerability in rasta-mouse pwnlift, published on 23 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-56815 in the wild and no public exploit code.

Affected product: rasta-mouse pwnlift. 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-56815/ (Markdown: https://insights.sbomify.com/CVE-2026-56815/index.md)
```

## Sources

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

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