CVE-2026-10849 is a heap-based out-of-bounds write in the Zephyr hawkBit device management client, affecting response handling in response_json_cb() within subsys/mgmt/hawkbit/hawkbit.c. The client accumulates the HTTP response body from the update server into a heap buffer sized only for the received body bytes, without reserving an additional byte for a terminating NUL character. After the full response is received, the code appends a terminator at response_data[downloaded_size], which writes one byte past the end of the allocation whenever the accumulated body length exactly matches the allocated size. The response length and fragmentation are controlled by the remote hawkBit server, making the flaw remotely reachable. In versions since 4.0.0, buffer growth to exactly downloaded_size plus body_len makes the out-of-bounds write deterministic for response bodies larger than the initial 1100-byte buffer. In versions before 4.0.0, an equality condition in the growth check can skip reallocation when the body length exactly matches the current allocation, also causing the terminating write to land out of bounds. The flaw affects Zephyr versions from 2.4.0 up to, but not including, 4.5.0.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.