Out-of-bounds Write in Bootloader

published 2026-11-04 8d ago modified 2026-11-05 6d ago also EUVD-2026-116698

cvss: 8.4; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.2%; EPSS 0.2% chance of exploitation in 30 days, percentile 15%
public exploits: 0; none known

Memory Corruption when processing firmware update data in Download mode due to a missing bounds check.

Is CVE-2026-80335 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: total
Assessed: 7d ago (2026-11-04)

Exploit prediction

0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by	version	score	vector
CNA	3.1	8.4	CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Affected products

Unisoc (Shanghai) Technologies Co., Ltd. Bootloader

Classification

Weakness

CWE-787 Out-of-bounds Write

References

unisoc.com /en/support/product-security-bulletin/2117823464494759937

Sources

CVE List CVE-2026-80335
NVD CVE-2026-80335

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.