CVE-2026-91191

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-30. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
34
EG Risk 34/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
10th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 29, 2026

Last Modified

September 30, 2026

Advisory Details (4)

Auto-updated Sep 29, 2026
Patch available. Sources: cisa.
generic

CSAF/csaf_files/OT/white/2026/icsa-26-272-01.json at develop · cisagov/CSAF · GitHub

https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-272-01.json
cisa Patch Available

Lantronix G520 Series Cellular Gateway | CISA

https://www.cisa.gov/news-events/ics-advisories/icsa-26-272-01
generic

Vulnerability Library | Lantronix

https://www.lantronix.com/technical-support/security-updates/vulnerability-disclosure-policy/vulnerability-library/
generic
https://ltrxdev.atlassian.net/wiki/spaces/LTRXTS/pages/1889828865/Latest+firmware+for+the+G520+Series+G526+G526RP+G527+G528

Vendor Advisories for CVE-2026-91191(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 23× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 08:01 UTCGHSA enrichment
  2. 2026-10-03 21:07 UTCEG score recompute
  3. 2026-10-03 21:07 UTCGHSA enrichment
  4. 2026-10-03 10:17 UTCGHSA enrichment
  5. 2026-10-02 23:27 UTCEG score recompute
  6. 2026-10-02 23:26 UTCGHSA enrichment
  7. 2026-10-02 12:30 UTCGHSA enrichment
  8. 2026-10-02 01:40 UTCEG score recompute
  9. 2026-10-02 01:40 UTCGHSA enrichment
  10. 2026-10-01 19:51 UTCEPSS rescore
  11. 2026-10-01 14:48 UTCGHSA enrichment
  12. 2026-10-01 03:58 UTCGHSA enrichment
  13. 2026-09-30 17:08 UTCGHSA enrichment
  14. 2026-09-30 16:25 UTCEG score recompute
  15. 2026-09-30 16:25 UTCGHSA enrichment
  16. 2026-09-30 15:44 UTCEG score recompute
  17. 2026-09-30 15:44 UTCGHSA enrichment
  18. 2026-09-30 15:04 UTCEPSS rescore
  19. 2026-09-30 09:19 UTCEG score recompute
  20. 2026-09-30 09:18 UTCGHSA enrichment
  21. 2026-09-29 22:27 UTCEG score recompute
  22. 2026-09-29 21:26 UTCEG score recompute
  23. 2026-09-29 21:23 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-91191?
CVE-2026-91191 is a high vulnerability published on September 29, 2026. 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.…
When was CVE-2026-91191 disclosed?
CVE-2026-91191 was first published on September 29, 2026, with the most recent update on September 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-91191 actively exploited?
CVE-2026-91191 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-91191?
CVE-2026-91191 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-91191?
A fix for CVE-2026-91191 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-91191 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-91191

Explore →

Is Your Infrastructure Affected by CVE-2026-91191?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs