Skip to main content
VulnerabilityPublished

CVE-2026-95823: zephyrproject zephyr · Use After Free

Affects zephyrproject zephyrSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 4.5.0 or 4.3.2 soon.

Data as of 18 Nov 2026, 14:35 UTC

CVSS 3.1 base score
7.5High
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.17.5
Patch
Available – fixed in 4.5.0, 4.3.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 18 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 17 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
  • >=2.3.0 <4.3.2
Fixed in
  • 4.3.2
GitHubzephyrpkg:github/zephyrOther threatsAffected
  • >=2.3.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. Users should upgrade to these or later versions to remediate the vulnerability. No additional mitigation actions are indicated by the vendor advisory.

Description

CVE-2026-95823 is a use-after-free vulnerability in the Zephyr project's TCP implementation affecting versions >=2.3.0 <4.3.2 and >=4.4.0 <4.5.0. The flaw occurs in tcp_pkt_linearize() when processing TCP headers that span multiple net_buf fragments, leading to improper freeing of buffers and potential memory corruption. An attacker can trigger this by sending a single crafted TCP segment with the header split across buffer boundaries, causing resource exhaustion or double free conditions. The issue is fixed in Zephyr versions 4.3.2 and 4.5.0.

References

Community reviews

Loading reviews…