Code execution via serial telegram off-by-one write
Published Sep 3, 2026 · Updated Sep 3, 2026
Buffer overflow in Core MOOS 10.4.0 and earlier allows physically proximate attackers to corrupt memory via a full serial telegram. CMOOSSerialPort::GetTelegram reads to the 1,000-byte stack-buffer limit, then writes a NUL terminator at index 1,000, one byte beyond the array. Control of a serial line or attached feed is required; the overwrite corrupts process memory and enables code execution, while unterminated input interrupts serial handling until restart.
Summary
What happened
Buffer overflow in Core MOOS 10.4.0 and earlier allows physically proximate attackers to corrupt memory via a full serial telegram. CMOOSSerialPort::GetTelegram reads to the 1,000-byte stack-buffer limit, then writes a NUL terminator at index 1,000, one byte beyond the array. Control of a serial line or attached feed is required; the overwrite corrupts process memory and enables code execution, while unterminated input interrupts serial handling until restart.
The record
- CVE
- CVE-2026-85454
- Published
- Sep 3, 2026
- Updated
- Sep 3, 2026
- Vendor
- themoos
- Product
- Core MOOS
- Classifications
- CWE-193
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 3, 2026CVE publishedPublication date reported by the CVE source.
- Sep 3, 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=0 <=10.4.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
- Serial telegram sanitizer 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