Skip to main content
VulnerabilityPublished Updated

CVE-2026-13351: zephyrproject-rtos Zephyr · Missing Release of Resource after Effective Lifetime

Affects zephyrproject-rtos ZephyrSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High · fixed in 4.3.1 : patch zephyrproject-rtos Zephyr soon.

Data as of 7 Nov 2026, 23:24 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.3.1, 4.2.2, 3.7.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jun 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 7 Nov 2026.

What to do

Upgrade zephyrproject-rtos Zephyr to 4.3.1, 4.2.2 or 3.7.2.

Affected software

ProductAffectedFixed in
zephyrproject-rtosZephyrAffected
  • >=4.3.0 <4.3.1
Fixed in
  • 4.3.1
zephyrproject-rtosZephyrAffected
  • >=4.0.0 <4.2.2
Fixed in
  • 4.2.2
zephyrproject-rtosZephyrAffected
  • <3.7.2
Fixed in
  • 3.7.2
GitHubZephyrpkg:github/ZephyrOther threatsAffected
  • <3.7.2
  • >=4.0.0 <4.2.2
  • >=4.3.0 <4.3.1
Fixed in
  • 3.7.2
  • 4.2.2
  • 4.3.1

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

AI-suggested

If you cannot patch yet, consider network-level filtering to block suspicious fragmented IPv6 packets if feasible.

Description

Zephyr's IPv6 network stack can be prevented from receiving or processing future incoming packets by sending a small number of maliciously fragmented IPv6 packets. When such a packet is handled by the fragment-header processing path, the associated RX network packet buffer (allocated from a memory slab) is not released back to the pool. Repeating the malicious packet exhausts all RX buffer slots, after which the device can no longer obtain RX buffers and stops receiving traffic, resulting in a denial of service.

References

Community reviews

Loading reviews…