CVE-2026-10643 Vulnerability Analysis & Exploit Details

CVE-2026-10643
Vulnerability Scoring

8.7
/10
Severe Risk

Cybersecurity professionals consider CVE-2026-10643 an immediate threat requiring urgent mitigation.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Local
    Vulnerability requires local system access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Changed
    Successful exploitation can impact components beyond the vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-10643 Details

Status: Modified

Last updated: 🕙 06 Aug 2026, 22:16 UTC
Originally published on: 🕛 28 Jun 2026, 00:16 UTC

Time between publication and last update: 39 days

CVSS Release: version 3

CVSS3 Source

vulnerabilities@zephyrproject.org

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:H

CVE-2026-10643 Vulnerability Summary

CVE-2026-10643: Zephyr's IP socket recvmsg() implementation (subsys/net/lib/sockets/sockets_inet.c, insert_pktinfo()) validated the user-supplied ancillary (msg_control) buffer using only the payload length (msg->msg_controllen < pktinfo_len) before writing a full control message consisting of an aligned cmsg header plus the payload. Because the check omitted the cmsg header size, a control buffer whose length falls in the under-checked window (e.g. 16-27 bytes for IPv4 IP_PKTINFO on a 64-bit target, where a single element actually occupies 28 bytes) passes the guard yet causes a fixed-size out-of-bounds write of up to one cmsg header (~12 bytes) past the end of the buffer. Under CONFIG_USERSPACE the recvmsg verifier allocates a kernel-heap copy of the control buffer sized to msg_controllen and runs the implementation against it, so the overflow corrupts kernel heap memory and is triggerable from an unprivileged userspace thread; in supervisor mode it corrupts the caller's buffer. The path is reachable on a UDP/IP socket with IP_PKTINFO/IPV6_RECVPKTINFO (or hoplimit/timestamping) enabled when the application calls recvmsg() with an undersized control buffer and a datagram is received; part of the overwritten bytes (the destination IP in ipi_addr) is influenced by the received packet. The fix makes the capacity check use NET_CMSG_SPACE(pktinfo_len) (aligned header + aligned data) and returns -ENOMEM when the buffer is too small. Affected: v3.6.0 through v4.4.0.

Assessing the Risk of CVE-2026-10643

Access Complexity Graph

The exploitability of CVE-2026-10643 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-10643

CVE-2026-10643 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-10643, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-10643, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: Low
    CVE-2026-10643 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: High
    CVE-2026-10643 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2026-10643 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2026-10643 References

External References

CWE Common Weakness Enumeration

CWE-787

Vulnerable Configurations

  • cpe:2.3:o:zephyrproject:zephyr:3.6.0:-:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:3.6.0:-:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:3.6.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:3.6.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:3.6.0:rc2:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:3.6.0:rc2:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:3.6.0:rc3:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:3.6.0:rc3:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:3.7.0:-:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:3.7.0:-:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:3.7.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:3.7.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:3.7.0:rc2:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:3.7.0:rc2:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:3.7.0:rc3:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:3.7.0:rc3:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:3.7.1:-:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:3.7.1:-:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:3.7.1:rc1:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:3.7.1:rc1:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:3.7.2:-:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:3.7.2:-:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:3.7.2:rc2:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:3.7.2:rc2:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.0.0:-:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.0.0:-:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.0.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.0.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.0.0:rc2:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.0.0:rc2:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.0.0:rc3:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.0.0:rc3:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.1.0:-:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.1.0:-:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.1.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.1.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.1.0:rc2:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.1.0:rc2:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.1.0:rc3:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.1.0:rc3:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.2.0:-:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.2.0:-:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.2.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.2.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.2.0:rc2:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.2.0:rc2:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.2.0:rc3:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.2.0:rc3:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.2.1:*:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.2.1:*:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.3.0:-:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.3.0:-:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.3.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.3.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.3.0:rc2:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.3.0:rc2:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.3.0:rc3:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.3.0:rc3:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.3.1:rc1:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.3.1:rc1:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.4.0:-:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.4.0:-:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.4.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.4.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.4.0:rc2:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.4.0:rc2:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.4.0:rc3:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.4.0:rc3:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.4.1:-:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.4.1:-:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-10643: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-97663 – The Customer Reviews for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Author Name in all versions up t...
  • CVE-2026-97641 – The Relevanssi – A Better Search plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content in all versions up to, and i...
  • CVE-2026-97637 – The JSON API Auth plugin for WordPress is vulnerable to Authentication Bypass via Cached Session Cookie Disclosure in all versions up to, and inclu...
  • CVE-2026-97634 – The Event Tickets and Registration plugin for WordPress is vulnerable to generic SQL Injection via the 'orderby' parameter in all versions up to, a...
  • CVE-2026-97342 – The JetFormBuilder — Dynamic Blocks Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'choice' Post Meta via Inser...