Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach MOOSDB on network
-
DeliveryPublish crafted PSHARE_CMD (cmd=output/input)
-
ExploitpShare opens listener on attacker address
-
ExecutionBus traffic redirected/duplicated to attacker
-
ImpactIntercept or tamper with sensor/control data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires network reachability to a MOOS community's MOOSDB and the ability to publish a MOOS variable (PSHARE_CMD) - MOOS provides no authentication, so any client with that reach qualifies. On vulnerable versions through 10.0.1 this works against default configurations because pShare called EnableCommandMessageFiltering(true) unconditionally and thus always honored PSHARE_CMD. The limiting factors are deployment-based rather than technical: the MOOSDB/pShare must be reachable by the attacker (typically these run on isolated vehicle/lab networks), and after the PR #20 patch exploitation additionally requires the operator to have explicitly set AllowRuntimeRouteChanges=true, which defaults to false. |
| Impact | The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N, VC:H/VI:H/VA:H, score 9.3) reflects a network-reachable, low-complexity, unauthenticated attack with high impact, which is consistent with the description: any publisher can reconfigure routing. The real-world caveat is deployment context - MOOS databases are typically run on trusted lab/vehicle networks and MOOS has no built-in authentication, so 'unauthenticated' here means 'any party with network reach to the MOOSDB.' There is no EPSS, KEV, or SSVC data provided; the finding is credited to VulnCheck with a published advisory. No public exploit code is referenced, so this is 'no public exploit identified at time of analysis' rather than confirmed exploitation. Given the niche footprint of MOOS, the practical priority is high for the specific robotics/autonomy operators who run essential-moos exposed on reachable networks, and low for the broader population. The provided VC:H/VI:H/VA:H is defensible but VA (availability) is the weakest of the three - the primary demonstrated impact is traffic redirection/duplication (confidentiality and integrity of the bus), with availability degradation being a secondary consequence. |
| Exploit ScenarioDerived | An attacker who can reach the MOOSDB on a robotics/autonomy network publishes a crafted PSHARE_CMD message with cmd=output pointing at an attacker-controlled address. pShare opens the new listener/route and begins duplicating live bus traffic (sensor, telemetry, or control variables) to the attacker, who can also use cmd=input to redirect traffic and tamper with delivery. No public PoC is referenced, but the attack requires only the ability to publish a single MOOS variable. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 03, 2026
Unauthorized runtime route reconfiguration in MOOS essential-moos pShare through 10.0.1 lets any client of the MOOS database issue PSHARE_CMD messages to open new listeners and redirect or duplicate inter-process bus traffic. Because pre-patch builds unconditionally subscribed to PSHARE_CMD, a remote unauthenticated attacker able to publish to the MOOSDB could reroute or mirror sensor/control traffic to attacker-controlled destinations without any credentials. The vendor patch (PR #20) is available and a source-level fix is confirmed, but no public exploit or active exploitation is identified at time of analysis.
RemediationAI
Apply the vendor fix from upstream PR https://github.com/themoos/essential-moos/pull/20 (commit 8e51cedcbd8de9781adec2e9cce354f51750a547); a released, tagged patched version is not independently confirmed from the input, so this is best described as an upstream fix available via PR/commit. The fix introduces a mission-file parameter, AllowRuntimeRouteChanges, which defaults to false, so after patching pShare no longer subscribes to or acts on PSHARE_CMD unless the mission explicitly opts in (and even then adds a 'belt and braces' guard that ignores stray PSHARE_CMD messages arriving by other paths). Operators who genuinely need runtime route changes should scope AllowRuntimeRouteChanges=true only to trusted deployments. Until patched, the practical compensating control is network isolation: restrict access to the MOOSDB/pShare ports to trusted hosts (firewall or VLAN segmentation) so untrusted parties cannot publish PSHARE_CMD - the trade-off is that any legitimate remote MOOS clients must be explicitly whitelisted. Avoid exposing the MOOS community to untrusted or internet-reachable networks.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
MOOS (Mission Oriented Operating Suite) is a publish/subscribe middleware widely used in marine and autonomous-vehicle robotics research, where a central MOOSDB brokers named variables between processes. pShare is the essential-moos process that bridges/forwards these variables across the network by managing routes and listeners. This flaw is CWE-862 (Missing Authorization): pShare accepts the runtime control variable PSHARE_CMD (with cmd=output/cmd=input parameters) from any MOOSDB publisher and acts on it to add listeners and routes at runtime, with no check that the sender is authorized to reconfigure the network topology. The affected component is cpe:2.3:a:themoos:essential-moos:*, specifically the command-message handling in Essentials/pShare/Share.cpp. The upstream diff shows the root cause: OnProcessCommandLine() previously called EnableCommandMessageFiltering(true) unconditionally, so pShare always subscribed to and acted on PSHARE_CMD.
Know when Essential Moos gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Any unauthenticated MOOSDB publisher can reconfigure routes remotely (AV:N/AC:L/PR:N); duplicating/redirecting bus traffic gives C:H/I:H, with availability only secondarily affected (A:L).
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
MOOS essential-moos pShare through 10.0.1 fails to properly authorize PSHARE_CMD messages, allowing any publisher to reconfigure network routes and listeners at runtime. Attackers can send crafted PSHARE_CMD messages with cmd=output or cmd=input parameters to open new listeners on arbitrary addresses and redirect or duplicate bus traffic to attacker-controlled destinations.
Executive ViewAI
MOOS essential-moos pShare versions through 10.0.1 allow unauthenticated remote attackers to redirect or duplicate sensor and control messages, compromising mission-critical autonomous systems and robotics platforms. Organizations using MOOS face immediate risk of loss of command and control, sensor spoofing, and operational sabotage. No public exploit is identified at time of analysis, but this critical-severity vulnerability with unauthenticated remote access requires urgent patching.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Essential Moos
View allRemote code execution in MOOS essential-moos pAntler through 10.0.1 lets unauthenticated attackers run arbitrary program
Unauthenticated UDP packet injection in MOOS essential-moos pMOOSBridge through version 10.0.1 allows any network-reacha
Unauthenticated UDP datagram injection in essential-moos pShare through 10.0.1 allows any network-reachable attacker to
Heap corruption in MOOS essential-moos through 10.0.1 allows unauthenticated remote attackers to crash the pMOOSBridge p
EUVD-2026-70807
GHSA-vrg5-259h-pjj5
NVD
CVE.org
EPSS
Exploit-DB