# CVE-2026-103398: OpenSave through 2.4.0 Arbitrary File Read and Write via Peer-Controlled Save Path

> Attackers can read and write arbitrary files by manipulating save paths in OpenSave, potentially compromising system integrity and data confidentiality.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/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:** 30 Sep 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-x83p-5c62-2g52

## What is CVE-2026-103398?

CVE-2026-103398 is a high-severity path traversal vulnerability in Liquid-co OpenSave, published on 30 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenSave through 2.4.0 fails to properly validate save paths supplied by paired peers in the manifest request handler. Attackers can specify arbitrary directories outside configured save locations to read and write files through manifest and sync routes.

Weakness: CWE-73 (External Control of File Name or Path)

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


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

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

## Is CVE-2026-103398 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-103398 is a high-severity path traversal vulnerability in Liquid-co OpenSave, published on 30 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-103398 in the wild and no public exploit code.

Affected product: Liquid-co OpenSave. 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-103398/ (Markdown: https://insights.sbomify.com/CVE-2026-103398/index.md)
```

## Sources

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

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