# CVE-2026-10678: NULL-pointer / out-of-bounds write in Zephyr MCTP I2C+GPIO target binding driven by an unauthenticated I2C controller > A malicious I2C bus master can trigger memory corruption or denial of service in Zephyr RTOS via unvalidated MCTP I2C+GPIO target writes. - **Severity:** High 8.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 21 Jul 2026 - **Updated:** 15 Oct 2026 - **Also known as:** GHSA-pmwm-5rcm-39rr ## What is CVE-2026-10678? CVE-2026-10678 is a high-severity memory corruption vulnerability in Zephyrproject Zephyr, published on 21 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description The MCTP-over-I2C+GPIO target binding in Zephyr (subsys/pmci/mctp/mctp_i2c_gpio_target.c) processes pseudo-register writes from an I2C bus master byte-by-byte in mctp_i2c_gpio_target_write_received() without validating the order or the receive buffer. In the affected versions the MCTP_I2C_GPIO_RX_MSG_ADDR (data) handler dereferences and writes through b->rx_pkt without checking that the receive buffer was allocated: a controller that selects the data register and writes a byte without first sending the length register (which is what allocates the buffer) causes a write of an attacker-chosen byte through a NULL/unallocated mctp_pktbuf pointer (i.e. into a small attacker-advanceable offset above address 0), producing memory corruption or a hard fault. The same handler also performs a write-then-check bounds test, allowing a one-byte heap overflow at data[255] when more than 255 data bytes are sent. Because the I2C target callback is invoked with raw bytes supplied by whatever device is the bus master and the binding performs no authentication, a malicious or malfunctioning controller on the bus can trigger these without any prior protocol state, leading to memory corruption and/or denial of service on the target device. The vulnerable code was introduced when the I2C+GPIO target binding was added and shipped in Zephyr v4.3.0 and v4.4.0. The fix defers allocation to the first data byte with a NULL check, treats a missing length as a zero-sized packet rejected by libmctp, and moves the bounds check before the store. Weakness: CWE-787 (Out-of-bounds Write), CWE-476 (NULL Pointer Dereference) ## Which versions are affected by CVE-2026-10678? It affects 1 product. Products: Zephyrproject Zephyr. ## How do I fix CVE-2026-10678? No fix has been published for CVE-2026-10678 yet. Limit exposure of the affected software until one is available. ## Is CVE-2026-10678 being exploited? There is no known exploitation of CVE-2026-10678 in the wild and no public exploit code. ## Other vulnerabilities in Zephyrproject Zephyr - [CVE-2026-5067](https://insights.sbomify.com/CVE-2026-5067/): Out-of-bounds read/write in HTTP WebSocket upgrade via non-null-terminated Sec-WebSocket-Key (critical 9.8) - [CVE-2022-3806](https://insights.sbomify.com/CVE-2022-3806/): Bluetooth HCI Error Handling Double Free (critical 9.8) - [CVE-2017-14199](https://insights.sbomify.com/CVE-2017-14199/): Memory corruption in getaddrinfo (critical 9.8) - [CVE-2018-1000800](https://insights.sbomify.com/CVE-2018-1000800/): Null dereference in n/a (critical 9.8) - [CVE-2021-3329](https://insights.sbomify.com/CVE-2021-3329/): DOS: Incorrect handling of the initial HCI ACL_MTU handshake packet leads to crash of bluetooth host layer (critical 9.6) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-10678 and fix it if it is affected. What it is: CVE-2026-10678 is a high-severity memory corruption vulnerability in Zephyrproject Zephyr, published on 21 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-10678 in the wild and no public exploit code. Affected product: Zephyrproject Zephyr. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-10678/ (Markdown: https://insights.sbomify.com/CVE-2026-10678/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-10678 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-10678 - OSV: https://osv.dev/vulnerability/CVE-2026-10678 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-10678/ Summaries are generated and may contain mistakes; the official description above is the record.