CVE-2026-10687

Rejected reason: This CVE Record has been rejected by the Zephyr Project CNA. Subsequent analysis, confirmed with the fix author, determined that the addressed defect does not apply to any released version of Zephyr: the affected code path exists only in unreleased development code, and no released branch is affected. As no released version is affected, this identifier is withdrawn.

Published

Jun 18, 2026

Last Modified

Jun 18, 2026

Status

Rejected

• CVE-2026-10681In Zephyr's userspace dynamic-objects subsystem, thread_idx_…7
• CVE-2026-10682The userspace verifier z_vrfy_log_filter_set() for the log_f…7.8
• CVE-2026-10683In the Synopsys DesignWare I2C driver (drivers/i2c/i2c_dw.c)…4.6
• CVE-2026-10684In subsys/debug/coredump/coredump_shell.c, print_coredump_hd…3
• CVE-2026-10685The Zephyr Bluetooth GATT client CCC-write response handler …7.6
• CVE-2026-10686Zephyr's IPv6 forwarding path re-sent routed unicast packets…7.5
• CVE-2026-10688A vulnerability was determined in ahujasid blender-mcp up to…5.5
• CVE-2026-1069GitLab has remediated an issue in GitLab CE/EE affecting all…7.5
• CVE-2026-10690A vulnerability was identified in wonderwhy-er DesktopComman…6.3
• CVE-2026-10691A security flaw has been discovered in wonderwhy-er DesktopC…4.3
• CVE-2026-10692A weakness has been identified in johnhuang316 code-index-mc…4.3
• CVE-2026-10693A security vulnerability has been detected in SourceCodester…6.3