Skip to main content
VulnerabilityPublished Updated

CVE-2026-32292: GL-iNet Comet KVM · Improper Restriction of Excessive Authentication Attempts

Affects GL-iNet Comet KVMSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.3 Critical : upgrade to 1.7.2 as a priority.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.

Contested

Critical score, yet low EPSS after six months
EPSS
0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.7.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade GL-iNet Comet KVM to 1.7.2.

Affected software

ProductAffectedFixed in
GL-iNetComet KVMAffected
  • <1.7.2
Fixed in
  • 1.7.2

AI-suggested

  1. Immediately isolate GL-iNet Comet KVM devices from public or untrusted networks to reduce exposure.
  2. Implement network-level protections such as firewall rules or VPN access to restrict management interface access to trusted administrators only.
  3. Deploy external brute-force mitigation tools like fail2ban or intrusion prevention systems to detect and block repeated failed login attempts targeting the KVM interface.
  4. Monitor authentication logs closely for unusual login patterns or repeated failures indicative of brute-force attempts.
  5. Where possible, enforce strong, complex passwords and consider multi-factor authentication if supported by the device or surrounding infrastructure.
  6. Engage with GL-iNet support channels to obtain updates or patches as they become available and apply them promptly.
  7. Consider alternative secure remote management solutions if immediate patching is not feasible.
  8. Conduct regular security assessments of remote management devices to identify and remediate similar vulnerabilities proactively.

Description

The GL-iNet Comet (GL-RM1) KVM web interface does not limit login requests, enabling brute-force attempts to guess credentials.

References

Community reviews

Loading reviews…