cve.bz

CVE-2026-40003 zte zx297520v3 firmware: Out-of-bounds Write

6.8 mediumEPSS 0.3%

Medium (6.8) in zte zx297520v3 firmware. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
ZTE ZX297520V3 BootROM contains a vulnerability that allows arbitrary memory writes via USB. Attackers can exploit the lack of target address validation in the USB download mode to write data to any location in BootROM runtime memory, thereby overwriting the stack, hijacking the execution flow, bypassing the Secure Boot signature verification mechanism, and achieving unauthorized code execution.

Severity

CVSS 3.1

6.8 medium
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 22nd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-05-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-787 Out-of-bounds Write
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-40003 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-40003?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-40003?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-40003 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-40003

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-40003](https://cve.bz/cve/badge/CVE-2026-40003.svg)](https://cve.bz/cve/CVE-2026-40003)

HTML:

<a href="https://cve.bz/cve/CVE-2026-40003"><img src="https://cve.bz/cve/badge/CVE-2026-40003.svg" alt="CVE-2026-40003"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
ZTE ZX297520V3 BootROM7520V3 chip

GitHub PoC (unverified)

Repositories on GitHub named after this CVE. Nobody has checked them and they are not scanned: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

References

Check your stackJSON