# CVE-2026-10687: Zephyr OS withdrawn vulnerability in unreleased development code

Source: https://junglewise.ai/threats/cve-2026-10687-zephyr-os-withdrawn-vulnerability-in-unreleased-development-code  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-06-18. Updated: 2026-06-20  
License: CC BY 4.0 with a link back

CVE-2026-10687 · Severity: info · CVSS 0 · Published 2026-06-18

This security identifier was withdrawn because the underlying issue only existed in unreleased development code. It does not affect any public or production versions of the Zephyr operating system. There is no risk to customers or existing deployments, and no action is required.

Technologies: [Zephyr Project Zephyr OS](https://junglewise.ai/threats/technologies/zephyr-os). Vendors: [Zephyr Project](https://junglewise.ai/threats/vendors/zephyr-project).

## Quick answers

**Is CVE-2026-10687 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-10687 being exploited in the wild.

**How severe is CVE-2026-10687?** Informational severity, with a CVSS score of 0, published 18 June 2026.

**Which products and versions are affected?** Zephyr Project Zephyr OS None (unreleased development code only).

**Is there a fix for CVE-2026-10687?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-10687 attacked?** It is in an operating system.

**Am I affected by CVE-2026-10687?** Check whether you run Zephyr Project Zephyr OS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The Zephyr Project CNA rejected this CVE after determining that the vulnerable code path was never included in a formal release or stable branch. The defect was identified and addressed within unreleased development code. Because no production versions are impacted, the vulnerability is considered non-existent for the purposes of security tracking. No technical remediation is necessary for users of released Zephyr versions.

## Affected products

- Zephyr Project Zephyr OS None (unreleased development code only)

## Timeline

- 2026-06-18: disclosed: CVE record published and immediately marked as rejected

## Related threats

- [Zephyr MCTP over USB use-after-free in packet buffer handling](https://junglewise.ai/threats/cve-2026-85032-the-mctp-over-usb-device-class-in-subsys-pmci-mctp-mctp-usb-c)
- [Zephyr arm64 MMU TLB invalidation memory isolation bypass](https://junglewise.ai/threats/cve-2026-79979-the-arm64-mmu-backend-invalidates-a-single-virtual-address-from)
- [Zephyr UpdateHub firmware client NULL pointer dereference in CoAP probe parsing](https://junglewise.ai/threats/cve-2026-76787-the-updatehub-firmware-over-the-air-client-parses-the-coap-probe)
- [CC1200 sub-GHz IEEE 802.15.4 driver buffer overflow in RX packet parsing](https://junglewise.ai/threats/cve-2026-75084-the-cc1200-sub-ghz-ieee-802-15-4-driver-takes-the-phy-packet)
- [Zephyr Bluetooth Link Layer memory leak in connection update](https://junglewise.ai/threats/cve-2026-19739-the-bluetooth-link-layer-control-procedure-code-in-subsys)