dbcve.org
Comet Gl Rm1 FirmwareOperating system · Gl Inet

CVE-2026-32292

HIGH · 7.5 CVSS v3.1 Published 2026-03-17
Fix available
A fix is available. Upgrade to 1.7.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
The GL-iNet Comet (GL-RM1) KVM web interface does not limit login requests, enabling brute-force attempts to guess credentials.

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

The GL-iNet Comet (GL-RM1) KVM web interface lacks rate limiting on authentication endpoints, allowing unlimited login attempts that facilitate credential brute-forcing.

MitigationImplement account lockout policies and rate limiting on the login interface to restrict failed authentication attempts within a defined time window.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Comet Gl Rm1 FirmwareOperating system
Affected:< 1.7.2

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 firmware version
    Access the GL-RM1 admin interface and navigate to System > Overview or check the footer of any admin page for the firmware version number. Alternatively, run 'cat /etc/os-release' or 'ubus call system board' via SSH to retrieve the installed firmware version.
    Affected if The firmware version is lower than 1.7.2 (e.g., 1.7.1, 1.6.x, etc.)
  2. Confirm KVM web interface is enabled
    Log into the GL-RM1 admin panel and check under Applications > KVM or Network > KVM to verify if the KVM web interface feature is enabled and accessible.
    Affected if The KVM web interface is enabled and accessible from the network
  3. Check for rate limiting on login endpoint
    Use a web proxy or curl to repeatedly send POST requests to the KVM login endpoint (typically /cgi-bin/kvm or /kvm/login) without observing any throttling or lockout behavior.
    Affected if Multiple rapid login attempts succeed without any HTTP 429 responses, CAPTCHA challenges, or account lockouts
  4. Verify authentication logs for brute-force evidence
    Access system logs via the admin interface (System > Logs) or run 'logread' via SSH and search for repeated failed authentication attempts from any single source IP.
    Affected if Logs show many failed login attempts from the same IP address without any blocking or rate limiting action taken by the system

You are affected if the GL-RM1 firmware version is below 1.7.2 AND the KVM web interface is enabled and accessible without rate limiting or account lockout protections.

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
Upgrade available Upgrade to 1.7.2 or later
Fixed in 1.7.2
Interim mitigation

Implement account lockout policies and rate limiting on the login interface to restrict failed authentication attempts within a defined time window.

Recommended fix High confidence

Firmware version 1.7.2 or later

  1. 1. Navigate to the GL-iNet admin interface for the Comet (GL-RM1) device
  2. 2. Go to the Firmware or System settings section
  3. 3. Locate the firmware upgrade option
  4. 4. Download firmware version 1.7.2 or later from the official GL-iNet support site (dl.gl-inet.com)
  5. 5. Upload the firmware file and apply the update
  6. 6. Wait for the device to reboot and complete the upgrade process
  7. 7. Verify the new firmware version is installed and the login page now implements rate limiting

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

Fix this in Comet Gl Rm1 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32292 — 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-32292 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