Code execution via empty event-registration pattern
Published Oct 22, 2025 · Updated Oct 22, 2025
Heap buffer overflow in OpenWrt ubusd before 24.10.4 allows local users to execute code via a crafted event registration. ubusd_alloc_event_pattern accepts a zero-length pattern and reads pattern[len - 1], accessing before the heap buffer and bypassing ubusd_acl_check. Any local ubus client reaches this parser before ACL checks, enabling daemon-context code execution and unauthorized event listening.
Summary
What happened
Heap buffer overflow in OpenWrt ubusd before 24.10.4 allows local users to execute code via a crafted event registration. ubusd_alloc_event_pattern accepts a zero-length pattern and reads pattern[len - 1], accessing before the heap buffer and bypassing ubusd_acl_check. Any local ubus client reaches this parser before ACL checks, enabling daemon-context code execution and unauthorized event listening.
The record
- CVE
- CVE-2025-62526
- Published
- Oct 22, 2025
- Updated
- Oct 22, 2025
- Vendor
- OpenWrt
- Product
- OpenWrt
- Classifications
- CWE-122, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 22, 2025CVE publishedPublication date reported by the CVE source.
- Oct 22, 2025Record 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=< 24.10.4
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