# CVE-2026-5959: GL.iNet GL-RM1/GL-RM10/GL-RM10RC/GL-RM1PE Factory Reset improper authentication


- **Severity:** High 7.5 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Apr 2026
- **Updated:** 13 Apr 2026
- **Also known as:** GHSA-69gc-w6vg-q56g

## What is CVE-2026-5959?

CVE-2026-5959 is a high-severity vulnerability in GL.iNet GL-RM1, published on 9 Apr 2026. 

### Official description

A security flaw has been discovered in GL.iNet GL-RM1, GL-RM10, GL-RM10RC and GL-RM1PE 1.8.1. Affected by this issue is some unknown functionality of the component Factory Reset Handler. Performing a manipulation results in improper authentication. The attack can be initiated remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. Upgrading to version 1.8.2 can resolve this issue. It is advisable to upgrade the affected component. The vendor was contacted early, responded in a very professional manner and quickly released a fixed version of the affected product.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-5959 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-5959 is a high-severity vulnerability in GL.iNet GL-RM1, published on 9 Apr 2026. 
Exploitation: There is no known exploitation of CVE-2026-5959 in the wild and no public exploit code.

Affected product: GL.iNet GL-RM1. 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-5959/ (Markdown: https://insights.sbomify.com/CVE-2026-5959/index.md)
```

## Sources

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

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