CVE-2026-9771: zephyrproject zephyr · Memory-safety
Affects zephyrproject zephyrSource CVE Database V5
Not known to be exploited · CVSS 8.8 High : upgrade to 4.4.2 or 4.3.2 soon.
Data as of 15 Nov 2026, 20:25 UTC
Thin evidence
One scorer or none| CNA (zephyr) | CVSS 3.1 | 8.8 |
|---|
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.4.2, 4.3.2
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 17 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Upgrade zephyrproject zephyr to 4.4.2 or 4.3.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| zephyrprojectzephyr | Affected
| Fixed in
|
| zephyrprojectzephyr | Affected
| Fixed in
|
GitHubzephyrpkg:github/zephyrOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability is fixed in Zephyr versions 4.3.2 and 4.4.2. Users should upgrade to these or later versions to remediate the issue. The fix involves kernel-side validation of device pointers passed to flash_copy() to ensure they are legitimate flash-driver kernel objects. No additional mitigation is required once patched.
Description
CVE-2026-9771 is a local privilege escalation vulnerability in the Zephyr RTOS affecting the flash_copy() system call on builds with CONFIG_USERSPACE enabled. The vulnerability arises because the kernel-side verification did not validate device pointers passed from user mode, allowing an unprivileged thread to supply forged device structures with attacker-controlled function pointers. This enables arbitrary code execution in supervisor mode, kernel crashes, or information disclosure. The issue is fixed by adding proper kernel object validation for the device pointers before dereferencing them.