{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-91191 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-91191 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-91191 is a high-severity vulnerability in Lantronix G520 Series, published on 29 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-91191 and fix it if it is affected.\n\nWhat it is: CVE-2026-91191 is a high-severity vulnerability in Lantronix G520 Series, published on 29 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-91191 in the wild and no public exploit code.\n\nAffected product: Lantronix G520 Series. 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-91191/ (Markdown: https://insights.sbomify.com/CVE-2026-91191/index.md)","id":"CVE-2026-91191","markdown":"https://insights.sbomify.com/CVE-2026-91191/index.md","name":"CVE-2026-91191","record":{"aliases":["GHSA-q7r9-65j5-94xj"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"cellular gateway","requires_auth":"none","summary":"Attackers can execute arbitrary code with root privileges by exploiting a hardcoded private key and disabled signature verification in the update mechanism.","user_interaction":"required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"icscert","cpe":[],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"The device's update mechanism includes conditions that allow unauthorized software packages to be accepted as authentic. During the boot process, the stock done function disables signature verification in the OPKG configuration before restoring optional packages from a writable, unsigned feed. Separately, the publicly distributed SDK contains the production private key whose corresponding public key is trusted by both stable and beta firmware builds. Either issue undermines package authenticity, and together they allow an attacker to provide packages that appear valid to the system. Even if signature enforcement is restored, the exposed production key enables an attacker to generate signatures that the device will continue to trust. An attacker who can supply a malicious package may be able to execute arbitrary code with root privileges during installation.","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":"Lantronix G520 Series Cellular Gateway Improper Verification of Cryptographic Signature","id":"CVE-2026-91191","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Flowable flowable-engine through 8.0.0 XXE via ProcessDiagramLayoutFactory","id":"CVE-2026-91197"},"packages":[],"prev":{"headline":"The GUIX binary resource loader never checks that a font page's glyph range is well formed.","id":"CVE-2026-91189"},"products":["G520 Series"],"published":"2026-09-29","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-09-30","vendors":["Lantronix"]},"summary":"Attackers can execute arbitrary code with root privileges by exploiting a hardcoded private key and disabled signature verification in the update mechanism.","url":"https://insights.sbomify.com/CVE-2026-91191/"}