Arbitrary firmware installation via self-contained MD5 hash
Published Mar 17, 2026 · Updated Mar 17, 2026
Firmware authentication failure in GL.iNet Comet (GL-RM1) before 1.8.2 allows attackers to install modified firmware. The updater trusts only an MD5 digest stored in the final 16 bytes of the same image, so modified content and a recomputed digest are accepted without a vendor signature. Exploitation requires access to the web interface or control of the update delivery path and grants persistent control through attacker-supplied firmware.
Summary
What happened
Firmware authentication failure in GL.iNet Comet (GL-RM1) before 1.8.2 allows attackers to install modified firmware. The updater trusts only an MD5 digest stored in the final 16 bytes of the same image, so modified content and a recomputed digest are accepted without a vendor signature. Exploitation requires access to the web interface or control of the update delivery path and grants persistent control through attacker-supplied firmware.
The record
- CVE
- CVE-2026-32290
- Published
- Mar 17, 2026
- Updated
- Mar 17, 2026
- Vendor
- GL.iNet
- Product
- Comet (GL-RM1)
- Classifications
- CWE-345, T1601.001
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Mar 17, 2026CVE publishedPublication date reported by the CVE source.
- Mar 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <*
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo