Quick answers
- Is CVE-2026-11812 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-11812 being exploited in the wild.
- How severe is CVE-2026-11812?
- Low severity, with a CVSS score of 2.5, published 10 August 2026.
- Which products and versions are affected?
- Zephyr RTOS <UNKNOWN>.
- Is there a fix for CVE-2026-11812?
- 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-11812 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-11812?
- Check whether you run Zephyr RTOS 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 vulnerability is a race condition and out-of-bounds write in subsys/mgmt/updatehub/updatehub.c. The UpdateHub management subsystem uses a single file-scope ctx structure to track CoAP block context, payload buffers, status codes, and socket state across multiple code paths. Access to ctx is not serialized, and the prepare_fds() function writes to ctx.fds[ctx.nfds] and increments ctx.nfds without bounds checking. Two independent execution paths mutate ctx concurrently: the background autohandler on the system workqueue and user-triggered operations via shell commands, API calls, or syscalls. When a second flow enters prepare_fds() while ctx.nfds is already 1, the write exceeds the one-element fds[1] array and corrupts adjacent ctx.sock/ctx.nfds members. Attack requires local access to invoke update operations and success depends on winning a timing race against the background handler. The fix adds mutex serialization and bounds checking.
Affected products
- Zephyr RTOS <UNKNOWN>
Timeline
- 2026-08-10: disclosed