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

Published Sep 30, 2026
·
Updated

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.

Affected Software

1 affected component
OpenSave<2.4.0-beta.1

Event History

Sep 30, 2026
CVE Published
via MITRE·02:48 PM
Data Sourced
via MITRE·02:48 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:22 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who is exposed to this issue?

OpenSave deployments using versions before 2.4.0-beta.1 are exposed when they use WAN relay requests and have rooms that an attacker can join with a known room code. Unpaired room members can target paired devices in those rooms.

2

What does an attacker need to exploit it?

The attacker needs the room code to join the room. After joining, they can obtain paired peer identifiers from announcements and spoof the RelayMessage From field in requests sent through the WAN relay.

3

What access can exploitation provide?

A successful attacker can impersonate a paired device to reach protected sync routes. The described targets include save data, snapshots, and file operations.

4

How can I determine whether my deployment is affected?

Check whether the OpenSave version is earlier than 2.4.0-beta.1 and whether WAN relay functionality is in use. Also assess whether room codes could be known by or disclosed to untrusted users, since knowledge of a room code enables joining the room.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203