Memory exhaustion via unbounded mux fragment count
Published Sep 3, 2026 · Updated Sep 4, 2026
Denial of service in MOOS-IvP 24.8.1 and earlier allows remote attackers to exhaust memory with a crafted BHV_IPF payload. Demuxer::addMuxPacket parses the payload's mux header without bounding its declared fragment count, and DemuxUnit allocates one string and flag entry per claimed fragment. Remote attackers need no credentials or user interaction; a 21-byte message declaring 900,000,000 fragments raised uFunctionVis memory use from 81 MB to 28.3 GB, interrupting the service.
Summary
What happened
Denial of service in MOOS-IvP 24.8.1 and earlier allows remote attackers to exhaust memory with a crafted BHV_IPF payload. Demuxer::addMuxPacket parses the payload's mux header without bounding its declared fragment count, and DemuxUnit allocates one string and flag entry per claimed fragment. Remote attackers need no credentials or user interaction; a 21-byte message declaring 900,000,000 fragments raised uFunctionVis memory use from 81 MB to 28.3 GB, interrupting the service.
The record
- CVE
- CVE-2026-85445
- Published
- Sep 3, 2026
- Updated
- Sep 4, 2026
- Vendor
- MOOS-IvP
- Product
- MOOS-IvP
- Classifications
- CWE-789, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 3, 2026CVE publishedPublication date reported by the CVE source.
- Sep 4, 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 <=24.8.1
What conditions does exploitation require?
What is affected?
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