dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-5959

MEDIUM · 6.6 CVSS v3.1 Published 2026-04-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A vulnerability in the Factory Reset Handler component of GL.iNet GL-RM1, GL-RM10, GL-RM10RC, and GL-RM1PE routers running firmware 1.8.1 allows remote attackers to manipulate factory reset functionality without proper authentication. The attack requires high complexity and is difficult to exploit, but could enable unauthorized device resets or potentially further compromise.

MitigationUpgrade affected GL.iNet router firmware from version 1.8.1 to version 1.8.2 to remediate the improper authentication vulnerability in the Factory Reset Handler.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify router model
    Log into the router admin interface or check the device label to determine if the model is GL-RM1, GL-RM10, GL-RM10RC, or GL-RM1PE
    Affected if Model is one of GL-RM1, GL-RM10, GL-RM10RC, or GL-RM1PE
  2. Check installed firmware version
    Access router admin panel (typically via web GUI at 192.168.1.1) and navigate to System > Firmware or System > Overview to view the current firmware version
    Affected if Firmware version is 1.8.1 (the affected version)
  3. Verify Factory Reset Handler accessibility
    Attempt to access the factory reset endpoint via the router's web API or check router logs for any unauthenticated reset requests. On GL.iNet routers, this may be found under /api/factory/reset or similar endpoints in the web interface.
    Affected if Factory reset functionality can be triggered without authentication prompts or credentials
  4. Confirm authentication is required for reset
    Test whether the factory reset function prompts for admin credentials when accessed. Review router authentication settings in System > Administration to verify admin password is enforced for sensitive operations.
    Affected if Factory reset can be performed without providing admin credentials

User is affected if running firmware 1.8.1 on a GL-RM1, GL-RM10, GL-RM10RC, or GL-RM1PE router with an unauthenticated Factory Reset Handler.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade affected GL.iNet router firmware from version 1.8.1 to version 1.8.2 to remediate the improper authentication vulnerability in the Factory Reset Handler.

Recommended fix High confidence

1.8.2

  1. Access the GL.iNet router's web administration interface by entering the device's IP address in a web browser
  2. Log in with administrator credentials
  3. Navigate to the 'System' or 'Firmware' settings section
  4. Locate the 'Firmware Upgrade' or 'OTA Update' option
  5. Download the firmware version 1.8.2 from the official GL.iNet support page (dl.gl-inet.com)
  6. Upload the 1.8.2 firmware file to the router
  7. Wait for the upgrade process to complete - do not power off the device during this process
  8. After the router reboots, verify the firmware version is now 1.8.2
Caveat Firmware upgrade may reset some configurations to defaults; backup configuration before upgrading if needed

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5959 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-5959 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data