CVE-2026-10849
Remote heap out-of-bounds write in hawkBit client allows heap corruption and likely DoS.
Is CVE-2026-10849 being exploited?
Not confirmed. CVE-2026-10849 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.33% probability of exploitation in the next 30 days.
How severe is CVE-2026-10849?
CVE-2026-10849 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-10849?
Yes. A fix has been recorded for CVE-2026-10849. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-10849 affect?
CVE-2026-10849 affects hawkBit device management client (subsys/mgmt/hawkbit), Zephyr-based devices using hawkBit client, Embedded IoT devices using hawkBit updates. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-10849?
Apply vendor patch; enforce authenticated update servers and restrict update sources.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote malicious or MITM update server triggers a heap OOB write, corrupting allocator metadata causing likely denial of service; allocator-dependent chance of further corruption/RCE.
Patch when possible
- affected>= 2.4.0 and < 4.4.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.