Root code execution via compromised package authentication
Published Sep 29, 2026 · Updated Sep 29, 2026
Improper package authentication in Lantronix G520 Series 2.6.0.4R6 stable allows attackers to run code as root via malicious packages. During boot, the stock done function disables OPKG signature checks before restoring packages from a writable unsigned feed; the public SDK also exposes a production signing key trusted by stable and beta firmware. Exploitation requires an attacker to supply a malicious package that the gateway subsequently installs.
Summary
What happened
Improper package authentication in Lantronix G520 Series 2.6.0.4R6 stable allows attackers to run code as root via malicious packages. During boot, the stock done function disables OPKG signature checks before restoring packages from a writable unsigned feed; the public SDK also exposes a production signing key trusted by stable and beta firmware. Exploitation requires an attacker to supply a malicious package that the gateway subsequently installs.
The record
- CVE
- CVE-2026-91191
- Published
- Sep 29, 2026
- Updated
- Sep 29, 2026
- Vendor
- Lantronix
- Product
- G520 Series
- Classifications
- T1553.002
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 29, 2026CVE publishedPublication date reported by the CVE source.
- Sep 29, 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=2.6.0.4R6 stable
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started