{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-32290 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-32290 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-32290 is a high-severity vulnerability in GL-iNet Comet KVM, published on 17 Mar 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-32290 and fix it if it is affected.\n\nWhat it is: CVE-2026-32290 is a high-severity vulnerability in GL-iNet Comet KVM, published on 17 Mar 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-32290 in the wild and no public exploit code.\n\nAffected product: GL-iNet Comet KVM. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-32290/ (Markdown: https://insights.sbomify.com/CVE-2026-32290/index.md)","id":"CVE-2026-32290","markdown":"https://insights.sbomify.com/CVE-2026-32290/index.md","name":"CVE-2026-32290","record":{"aliases":["GHSA-j5q3-pwqh-x9p9"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"KVM device","requires_auth":"none","summary":"Attackers can bypass firmware verification on GL-iNet Comet KVM devices to install malicious firmware, leading to full device compromise.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"cisa-cg","cpe":[{"product":"comet_gl-rm1_firmware","vendor":"gl-inet"}],"cvss":{"score":7,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"GL-iNet Comet (GL-RM1) KVM insufficient firmware verification","id":"CVE-2026-32290","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"GL-iNet Comet (GL-RM1) KVM unauthenticated root access via UART serial console","id":"CVE-2026-32291"},"packages":[],"prev":{"headline":"JsBraceDepth Context Tracking Bugs (XSS) in html/template","id":"CVE-2026-32289"},"products":["Comet KVM"],"published":"2026-03-17","related":[{"cvss_score":9.3,"headline":"GL-iNet Comet (GL-RM1) KVM insufficient login rate-limiting","id":"CVE-2026-32292","kev_date_added":null,"published":"2026-03-17"},{"cvss_score":7,"headline":"GL-iNet Comet (GL-RM1) KVM unauthenticated root access via UART serial console","id":"CVE-2026-32291","kev_date_added":null,"published":"2026-03-17"},{"cvss_score":6.3,"headline":"GL-iNet Comet (GL-RM1) KVM insufficient certificate validation","id":"CVE-2026-32293","kev_date_added":null,"published":"2026-03-17"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-03-23","vendors":["GL-iNet"]},"summary":"Attackers can bypass firmware verification on GL-iNet Comet KVM devices to install malicious firmware, leading to full device compromise.","url":"https://insights.sbomify.com/CVE-2026-32290/"}