CVE-2026-32293: GL-iNet Comet KVM · Improper Certificate Validation
Affects GL-iNet Comet KVMSource CVE Database V5
Not known to be exploited · CVSS 3.7 Low : upgrade to 1.7.2 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.7.2
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 17 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| GL-iNetComet KVM | Affected
| Fixed in
|
AI-suggested
To mitigate CVE-2026-32293, organizations should implement the following specific measures: 1) Monitor GL-iNet vendor communications closely for firmware updates or patches addressing certificate validation and apply them promptly. 2) Employ network segmentation and strict access controls to limit the ability of attackers to perform man-in-the-middle attacks on device provisioning traffic, especially during boot-up. 3) Use network security tools such as TLS interception detection, anomaly-based intrusion detection systems, and certificate pinning where possible to detect or prevent unauthorized interception of provisioning connections. 4) Consider deploying VPNs or encrypted tunnels for device management traffic to reduce exposure to MitM attacks. 5) Where feasible, perform manual certificate provisioning or validation as a temporary workaround until a patch is available. 6) Maintain an inventory of all GL-iNet Comet KVM devices and monitor their connectivity status to quickly identify provisioning failures that may indicate exploitation attempts. 7) Educate network administrators about the risks of improper certificate validation and the importance of securing provisioning channels.
Description
The GL-iNet Comet (GL-RM1) KVM connects to a GL-iNet site during boot-up to provision client and CA certificates. The GL-RM1 does not verify certificates used for this connection, allowing an attacker-in-the-middle to serve invalid client and CA certificates. The GL-RM1 will attempt to use the invalid certificates and fail to connect to the legitimate GL-iNet KVM cloud service.
References
- eclypsium.com/blog/your-kvm-is-the-weak-link-how-30-dollar-devices-can-own-your-entire-network/ (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-32293 (opens in a new tab)
- raw.githubusercontent.com/cisagov/CSAF/develop/csaf_files/IT/white/2025/va-26-076-01.json (opens in a new tab)
- dl.gl-inet.com/release/kvm/release/RM1/1.7.2 (opens in a new tab)