CVE-2026-39880: Remnawave Backend is the backend for the Remnawave proxy and user management solution

Q: How do I fix CVE-2026-39880?

remnawave backend: upgrade to newer than 2.7.4. Exact commands for each OS are on this page.

Q: Is CVE-2026-39880 being exploited?

CVE-2026-39880 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-39880 affect?

CVE-2026-39880 affects remnawave backend. Severity is medium (CVSS 5.0). Remnawave Backend is the backend for the Remnawave proxy and user management solution. Prior to 2.7.5, a glitch in the HWID device registration logic allows an authenticated user to bypass the configured limit for HWID devices and register

Q: How urgent is CVE-2026-39880?

Priority 24/100. Public exploit reference

Routine

MEDIUM 5.0UPGRADE

CVE-2026-39880 is a medium-severity flaw (CVSS 5.0) affecting remnawave backend. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Remnawave Backend is the backend for the Remnawave proxy and user management solution. Prior to 2.7.5, a glitch in the HWID device registration logic allows an authenticated user to bypass the configured limit for HWID devices and register more devices than expected, allowing them to resell subscriptions and consume excessive traffic. This vulnerability is fixed in 2.7.5.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	5.0 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.2% (top 92%)
CISA exploited list	No
Weakness	CWE-362
Published	2026-04-08
Last modified	2026-07-24

Publisher (CNA): GitHub, Inc. · Vendor: remnawave

Last updated 2026-07-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-04-08 20:16 UTCPublished CVE record published
2026-07-24 21:10 UTCUpdated Record last modified

remnawave remnawave backend UPGRADE

Affected: <= 2.7.4

Fixed in: newer than 2.7.4

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy remnawave-backend || rpm -q remnawave-backend || remnawave-backend --version

2. UPGRADE to newer than 2.7.4 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade remnawave-backend

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade remnawave-backend

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-39880?

remnawave backend: upgrade to newer than 2.7.4. Exact commands for each OS are on this page.

Is CVE-2026-39880 being exploited?

CVE-2026-39880 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-39880 affect?

CVE-2026-39880 affects remnawave backend. Severity is medium (CVSS 5.0). Remnawave Backend is the backend for the Remnawave proxy and user management solution. Prior to 2.7.5, a glitch in the HWID device registration logic allows an authenticated user to bypass the configured limit for HWID devices and register

How urgent is CVE-2026-39880?

Priority 24/100. Public exploit reference

References

← Back to latest CVEs