# CVE-2026-103397: OpenSave before 2.4.0-beta.1 Authentication Bypass via Spoofed Relay Sender

> Attackers can bypass authentication by spoofing relay sender identities to access protected sync routes, read data, and modify files in OpenSave.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Sep 2026
- **Updated:** 2 Oct 2026
- **Also known as:** GHSA-m7pc-whc6-fxc7

## What is CVE-2026-103397?

CVE-2026-103397 is a medium-severity authentication bypass vulnerability in Liquid-co OpenSave, published on 30 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenSave before 2.4.0-beta.1 fails to validate sender identity in WAN relay requests, allowing unpaired room members to impersonate paired devices by spoofing the RelayMessage From field. Attackers who know the room code can join, read paired peer identifiers from announcements, and send forged requests to access protected sync routes including save data, snapshots, and file operations.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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


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

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

## Is CVE-2026-103397 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-103397 is a medium-severity authentication bypass vulnerability in Liquid-co OpenSave, published on 30 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-103397 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-103397/ (Markdown: https://insights.sbomify.com/CVE-2026-103397/index.md)
```

## Sources

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

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