# CVE-2026-57863: Crater Invoice 6.0.6 Path Traversal RCE via update/unzip endpoint

> Authenticated company owners can achieve remote code execution by uploading crafted ZIP archives with path traversal sequences to the self-update endpoint.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-227x-v64x-3fq7

## What is CVE-2026-57863?

CVE-2026-57863 is a high-severity path traversal vulnerability in crater-invoice-inc crater, published on 25 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Crater Invoice through 6.0.6 contains a path traversal vulnerability in the self-update API that allows authenticated company owners to write arbitrary files outside the intended extraction directory by supplying crafted ZIP archives with ../ sequences to the unzip endpoint. Attackers can exploit unsanitized ZIP entry names passed to PHP's ZipArchive::extractTo() to write arbitrary PHP files into the web-accessible public directory and achieve remote code execution on the server.

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

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


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

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

## Is CVE-2026-57863 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-57863 is a high-severity path traversal vulnerability in crater-invoice-inc crater, published on 25 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-57863 exists.

Affected product: crater-invoice-inc crater. 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-57863/ (Markdown: https://insights.sbomify.com/CVE-2026-57863/index.md)
```

## Sources

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

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