Skip to main content
VulnerabilityPublished

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

Affects zephyrproject zephyrSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 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.3Medium
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.3
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:N/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
  • >=3.0.0 <4.3.2
Fixed in
  • 4.3.2
GitHubzephyrpkg:github/zephyrOther threatsAffected
  • >=3.0.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 issue. No additional mitigation is required as the fix explicitly adds necessary NULL pointer checks and rejects invalid arguments.

Description

CVE-2026-93672 is a memory-safety vulnerability in the Zephyr project's Bluetooth ATT implementation. The function bt_att_find_req_by_user_data() dereferences a pointer without checking for NULL, leading to a potential null pointer read. This can cause a fatal error and device reset on platforms that trap near-NULL reads. The issue is triggered via the public bt_gatt_cancel() API and related Bluetooth GATT operations. The vulnerability impacts availability but does not lead to memory corruption or information disclosure. It affects Zephyr versions from 3.0.0 up to but not including 4.3.2 and from 4.4.0 up to but not including 4.5.0. Fixed in versions 4.3.2 and 4.5.0.

References

Community reviews

Loading reviews…