CVE-2026-91191

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in, but needs a user to act. High risk of data exposure, data tampering, service disruption.

Exploit odds

0.2% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2026-09-17 19:24 UTC ReservedThe CVE id was reserved by its CNA
2. 2026-09-29 22:19 UTC PublishedDisclosed publicly on CVE.org and NVD
3. 2026-09-30 16:46 UTC Last updatedMost recent change to the record

Details

Published

2026-09-29 22:19 UTC

Last modified

2026-09-30 16:46 UTC

Exploit probability

0.2% · EPSS, next 30 days

Weakness

CWE-347

Record status

Awaiting Analysis

Attack profile CVSS 4.0 · 7.7

Attack vector

Network

Complexity

Low

Attack requirements

Present

Privileges needed

None

User interaction

Passive

Confidentiality

High

Integrity

High

Availability

High