Skip to main content
VulnerabilityPublished

CVE-2026-93667: zephyrproject zephyr · Memory-safety

Affects zephyrproject zephyrSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.9 Medium : upgrade to 4.5.0 or 4.3.2 when convenient.

Data as of 16 Nov 2026, 21:36 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (zephyr)CVSS 3.15.9
Patch
Available – fixed in 4.5.0, 4.3.2
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
zephyrprojectzephyrAffected
  • >=4.4.0 <4.5.0
Fixed in
  • 4.5.0
zephyrprojectzephyrAffected
  • >=4.2.0 <4.3.2
Fixed in
  • 4.3.2
GitHubzephyrpkg:github/zephyrOther threatsAffected
  • >=4.2.0 <4.3.2
  • >=4.4.0 <4.5.0
Fixed in
  • 4.3.2
  • 4.5.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in Zephyr versions 4.3.2 and 4.5.0 that drops packets on interfaces that are not Virtual L2 interfaces, eliminating the faulty indirect call. Users should upgrade to these fixed versions to remediate the vulnerability. No additional mitigation is required beyond applying the official patch.

Description

CVE-2026-93667 is a memory-safety vulnerability in the Zephyr project affecting the virtual L2 receive handler. It arises from a fall-through code path that incorrectly treats non-virtual interfaces as virtual ones, leading to mistyped indirect calls. This can cause undefined behavior such as crashes and uncontrolled memory corruption when processing specially crafted 802.1Q-tagged Ethernet frames. No authentication or user interaction is required to trigger the issue. The flaw affects Zephyr versions >=4.2.0 <4.3.2 and >=4.4.0 <4.5.0 and is fixed in versions 4.3.2 and 4.5.0.

References

Community reviews

Loading reviews…