EUVD-2026-70783

MOOS-IvP pMarineViewer through 24.8.1 fails to limit the number of tracked node identities from NODEREPORT messages, allowing attackers to exhaust memory by supplying unbounded distinct node names. Attackers can publish crafted NODEREPORT data to cause memory exhaustion and stall the operator...

EUVD-2026-70790

MOOS-IvP through 24.8.1 fails to properly validate variable names extracted from alog files in the SplitHandler, allowing attackers to write files outside the split directory. Attackers can supply crafted alog files with backslash sequences in variable names to escape the output directory and...

EUVD-2026-70780

MOOS-IvP versions through 24.8.1 contain a quadratic processing vulnerability in uFldNodeComms where each new node identity creates a ledger entry and triggers all-pairs distribution work. Attackers can supply unbounded distinct node names in reports to drive the shoreside broker into quadratic...

EUVD-2026-70782

MOOS-IvP uFldShoreBroker through 24.8.1 fails to limit the number of claimed communities stored in parallel vectors within ShoreBroker::handleMailNodePing. A single publisher can supply unbounded distinct community names to grow retained state and per-pass work without limit, causing memory...

EUVD-2026-70779

MOOS-IvP through 24.8.1 contains a denial of service vulnerability in the Demuxer::addMuxPacket function that trusts the packet count declared in mux headers without validation. Attackers can declare arbitrarily large packet counts to trigger unbounded memory allocation, exhausting system resourc...

EUVD-2026-70781

MOOS-IvP pRealm through version 24.8.1 accepts unbounded REALMCASTREQ subscriptions without validating duration or variable list limits. Attackers can register long-lived pipeways with many variables to cause pRealm to generate excessive output indefinitely, exhausting system resources...

EUVD-2026-70778

MOOS-IvP through 24.8.1 contains a buffer over-read vulnerability in isQuoted, isBraced, and isChevroned functions that strip whitespace but index using the original string length. Attackers can send NODEREPORT messages with leading or trailing whitespace to read past buffer bounds and access...

EUVD-2026-70803

MOOS-IvP through 24.8.1 contains multiple buffer overflow vulnerabilities in IvP function string decoders that trust attacker-controlled length fields without validation. Attackers can craft malicious encoded strings with mismatched declared and actual field lengths to overflow heap and stack...

EUVD-2026-70802

MOOS-IvP through 24.8.1 contains a buffer overflow vulnerability in StringToIvPFunction where dimension, piece, and degree counts from encoded BHVIPF payloads are used as allocation sizes and loop bounds without validation. Attackers can supply crafted payloads with mismatched dimension values to...

EUVD-2026-70805

MOOS-IvP uFldNodeBroker through 24.8.1 fails to validate the source of TRYSHOREHOST messages on the vehicle bus, allowing any publisher to enroll attacker-controlled shore routes. Attackers can publish malicious shore route messages to receive bridged vehicle traffic including sensor data and...

EUVD-2026-70806

MOOS-IvP uFldShoreBroker through 24.8.1 fails to verify node ping authenticity before creating outbound bridge routes. Attackers can publish NODEBROKERPING messages with crafted HostRecord data to redirect bridged variables to attacker-controlled addresses...

EUVD-2026-70801

MOOS-IvP through 24.8.1 contains a remote code execution vulnerability in alogsplit's SplitHandler::handlePreCheckSplitDir function that fails to sanitize shell metacharacters in log file pathnames. Attackers can embed shell syntax in log file names or the --dir parameter to execute arbitrary...

EUVD-2026-70811

MOOS-IvP uFldNodeComms through 24.8.1 trusts the source node identity from the message body rather than validating it from the connection source. Attackers can craft NODEMESSAGE packets with spoofed source identities to impersonate other nodes and post arbitrary variable notifications without...

EUVD-2026-70815

MOOS-IvP iSay through 24.8.1 contains a remote code execution vulnerability in the SAYMOOS variable handler that passes unsanitized text to a shell command. Attackers can publish SAYMOOS messages containing backticks or command substitution syntax to execute arbitrary commands as the iSay process...

EUVD-2026-70814

MOOS-IvP uMemWatch through 24.8.1 constructs shell commands from attacker-chosen MOOS client names without sanitization. Attackers can inject shell metacharacters into client names to execute arbitrary commands as the uMemWatch process user through unquoted redirection targets in system calls...

CVE-2026-85456

MOOS-IvP through 24.8.1 fails to properly validate variable names extracted from alog files in the SplitHandler, allowing attackers to write files outside the split directory. Attackers can supply crafted alog files with backslash sequences in variable names to escape the output directory and...

CVE-2026-85445

MOOS-IvP through 24.8.1 contains a denial of service vulnerability in the Demuxer::addMuxPacket function that trusts the packet count declared in mux headers without validation. Attackers can declare arbitrarily large packet counts to trigger unbounded memory allocation, exhausting system resourc...

CVE-2026-85446

MOOS-IvP versions through 24.8.1 contain a quadratic processing vulnerability in uFldNodeComms where each new node identity creates a ledger entry and triggers all-pairs distribution work. Attackers can supply unbounded distinct node names in reports to drive the shoreside broker into quadratic...

CVE-2026-85444

MOOS-IvP through 24.8.1 contains a buffer over-read vulnerability in isQuoted, isBraced, and isChevroned functions that strip whitespace but index using the original string length. Attackers can send NODEREPORT messages with leading or trailing whitespace to read past buffer bounds and access...

CVE-2026-85447

MOOS-IvP pRealm through version 24.8.1 accepts unbounded REALMCASTREQ subscriptions without validating duration or variable list limits. Attackers can register long-lived pipeways with many variables to cause pRealm to generate excessive output indefinitely, exhausting system resources...