Pre-auth daemon crash via message-length underflow
Published Jul 7, 2026 · Updated Jul 7, 2026
Integer underflow in OpenWrt before 25.12.5 allows remote attackers on the local network to crash the Emergency Access Daemon. In handle_send_a(), a zero message length wraps to -1, bypasses the signed upper-bound check, and reaches memcpy as SIZE_MAX against a 257-byte buffer. Exposure requires EAD to be enabled and reachable on UDP port 56026; a valid local username is sufficient, and a successful packet interrupts emergency recovery access.
Summary
What happened
Integer underflow in OpenWrt before 25.12.5 allows remote attackers on the local network to crash the Emergency Access Daemon. In handle_send_a(), a zero message length wraps to -1, bypasses the signed upper-bound check, and reaches memcpy as SIZE_MAX against a 257-byte buffer. Exposure requires EAD to be enabled and reachable on UDP port 56026; a valid local username is sufficient, and a successful packet interrupts emergency recovery access.
The record
- CVE
- CVE-2026-55490
- Published
- Jul 7, 2026
- Updated
- Jul 7, 2026
- Vendor
- OpenWrt
- Product
- OpenWrt
- Classifications
- CWE-191, T1499.004
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 7, 2026CVE publishedPublication date reported by the CVE source.
- Jul 7, 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=< 25.12.5
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-9558-77jp-g3fw protocol 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