Device-wide network disruption via leaked UpdateHub sockets
Published Aug 10, 2026 · Updated Aug 10, 2026
Denial of service in Zephyr RTOS 2.0.0 through 4.4.1 allows remote attackers to exhaust network sockets via failed UpdateHub connections. The start_coap_client() error path tests ret > 0 after setting ret to -1, so failed DTLS setup or connection skips cleanup and the next attempt overwrites ctx.sock. Builds with CONFIG_UPDATEHUB enabled leak one descriptor per failed attempt until device-wide networking degrades and a reboot restores service.
Summary
What happened
Denial of service in Zephyr RTOS 2.0.0 through 4.4.1 allows remote attackers to exhaust network sockets via failed UpdateHub connections. The start_coap_client() error path tests ret > 0 after setting ret to -1, so failed DTLS setup or connection skips cleanup and the next attempt overwrites ctx.sock. Builds with CONFIG_UPDATEHUB enabled leak one descriptor per failed attempt until device-wide networking degrades and a reboot restores service.
The record
- CVE
- CVE-2026-11811
- Published
- Aug 10, 2026
- Updated
- Aug 10, 2026
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-772, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 10, 2026CVE publishedPublication date reported by the CVE source.
- Aug 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.0.0 <4.4.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo