dbcve.org
Comet Gl Rm1 FirmwareOperating system · Gl Inet

CVE-2026-32291

MEDIUM · 6.8 CVSS v3.1 Published 2026-03-17
Fix available
A fix is available. Upgrade to 1.8.2 or later.
See remediation →
73/100
Remediation priority · Elevated
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 before 1.8.2 does not require authentication on the UART serial console. This attack requires physically opening the device and connecting to the UART pins.

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 · moderate confidence

The GL-iNet Comet (GL-RM1) KVM devices before firmware version 1.8.2 expose an unauthenticated UART serial console. An attacker with physical access who can open the device and connect to the UART pins can obtain console access without any authentication credentials, potentially gaining full control of the device.

MitigationUpgrade the GL-RM1 firmware to version 1.8.2 or later, which adds authentication to the UART console. As an additional physical security control, consider placing the device in a secured location or using tamper-evident enclosures to limit physical access.

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

CVSS:3.1/AV:P/AC:L/PR:N/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 the device model
    Locate the device label or check the web admin interface (usually at 192.168.1.1) for the exact model number - look for GL-RM1 or Comet
    Affected if The device is a GL-iNet GL-RM1 (Comet)
  2. Check the installed firmware version
    Access the router web interface, navigate to System > Overview or Status page, and locate the Firmware Version field. Alternatively, SSH to the device and run: cat /etc/os-release or gload status
    Affected if The firmware version displayed is below 1.8.2 (for example, 1.7.0, 1.6.x, etc.)
  3. Verify the UART interface accessibility
    This requires physical inspection: open the device case and examine the PCB for exposed UART pins (typically 4 pins in a row: RX, TX, GND, VCC) near the CPU or flash chip. Check if the pins are easily accessible and not physically protected
    Affected if UART pins are present and accessible without special tools or removal of protective covers
  4. Confirm if authentication is required on console boot
    If you have legitimate physical access, connect a USB-to-serial adapter to the UART pins (baud rate 115200, 8N1) and power on the device. Observe if the boot process prompts for any login credentials before providing shell access
    Affected if The console provides a shell or login prompt immediately without requiring any username/password authentication

You are affected if you have a GL-RM1 device running firmware version below 1.8.2 and the UART interface is physically accessible on the device PCB.

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.8.2 or later
Fixed in 1.8.2
Interim mitigation

Upgrade the GL-RM1 firmware to version 1.8.2 or later, which adds authentication to the UART console. As an additional physical security control, consider placing the device in a secured location or using tamper-evident enclosures to limit physical access.

Recommended fix Moderate confidence

GL-RM1 Firmware 1.8.2

  1. Download the GL-iNet Comet (GL-RM1) firmware version 1.8.2 or later from the official GL-iNet download site (dl.gl-inet.com)
  2. Verify the firmware file integrity using checksums provided on the download page
  3. Access the device's web administration interface
  4. Navigate to the firmware upgrade section (typically under System > Firmware or Administration)
  5. Upload and apply the firmware version 1.8.2
  6. Allow the device to complete the upgrade process and reboot
  7. After reboot, verify the new firmware version is installed

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
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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