Skip to main content
VulnerabilityPublished Updated

CVE-2026-32290: GL-iNet Comet KVM · Insufficient Verification of Data Authenticity

Affects GL-iNet Comet KVMSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.0 High : upgrade to 1.8.2 soon.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score
7.0High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.8.2
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:A/VC:N/VI:H/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 29 Oct 2026.

What to do

Upgrade GL-iNet Comet KVM to 1.8.2.

Affected software

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

AI-suggested

  1. Immediately update all GL-iNet Comet KVM devices to firmware version 1.8.2 or later, which addresses this vulnerability.
  2. Implement strict network segmentation and access controls to limit local network access to KVM devices, reducing the risk of MitM attacks.
  3. Use secure, authenticated channels (e.g., VPNs, TLS) for firmware updates to prevent interception or tampering.
  4. Disable automatic or user-initiated firmware updates unless performed by trusted administrators.
  5. Monitor network traffic for unusual update attempts or anomalies in device behavior post-update.
  6. Employ cryptographic verification mechanisms beyond MD5, such as digital signatures, to validate firmware authenticity.
  7. Educate personnel responsible for device maintenance about the risks of firmware tampering and the importance of verifying update sources.
  8. Consider deploying intrusion detection systems to detect potential MitM or update server compromise attempts.
  9. Regularly audit device firmware versions and integrity to detect unauthorized changes promptly.

Description

The GL-iNet Comet (GL-RM1) KVM before version 1.8.2 does not sufficiently verify the authenticity of uploaded firmware files. An attacker-in-the-middle or a compromised update server could modify the firmware and the corresponding MD5 hash to pass verification.

References

Community reviews

Loading reviews…