Remote code execution via oversized IPv4 port suffix
Published Jul 12, 2026 · Updated Jul 12, 2026
Stack buffer overflow in Zephyr RTOS 1.9.0 through 4.4.0 allows remote attackers to corrupt memory via a crafted IPv4 address-and-port string. parse_ipv4() copies the suffix after the colon into a 17-byte stack buffer using the unbounded input length instead of the destination size. Exposure requires an application to resolve a network-influenced address string; exploitation can crash the device or hijack control flow.
Summary
What happened
Stack buffer overflow in Zephyr RTOS 1.9.0 through 4.4.0 allows remote attackers to corrupt memory via a crafted IPv4 address-and-port string. parse_ipv4() copies the suffix after the colon into a 17-byte stack buffer using the unbounded input length instead of the destination size. Exposure requires an application to resolve a network-influenced address string; exploitation can crash the device or hijack control flow.
The record
- CVE
- CVE-2026-10666
- Published
- Jul 12, 2026
- Updated
- Jul 12, 2026
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-121
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 12, 2026CVE publishedPublication date reported by the CVE source.
- Jul 12, 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=1.9.0 <4.5.0
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
- GHSA-532c-7g7f-jhmh proof of conceptproof of concept · demonstrated
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