CVE-2026-93670: zephyrproject zephyr · Bounds
Affects zephyrproject zephyrSource CVE Database V5
Not known to be exploited · CVSS 3.5 Low : upgrade to 4.5.0 or 4.3.2 when convenient.
Data as of 16 Nov 2026, 21:36 UTC
Thin evidence
One scorer or none| CNA (zephyr) | CVSS 3.1 | 3.5 |
|---|
- Patch
- Available – fixed in 4.5.0, 4.3.2
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 16 Nov 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 16 Nov 2026.
What to do
Upgrade zephyrproject zephyr to 4.5.0 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
Fixed versions 4.3.2 and 4.5.0 of Zephyr are available and address this issue. Users should upgrade to these or later versions to remediate the vulnerability. No additional mitigations are required as the issue is fixed in these releases.
Description
CVE-2026-93670 is a vulnerability in the Synopsys DesignWare I3C controller driver within the Zephyr project. The driver incorrectly handles the exhaustion of the Device Address Table (DAT) slots due to a type mismatch that disables the exhaustion guard. This leads to out-of-bounds memory writes beyond the allocated array and hardware table. The impact is limited to potential corruption of driver state, reserved registers, or driver instability. The vulnerability can be triggered locally via the I3C bus by attaching more devices than the DAT can hold. No network attack vector exists.