Description
MOOS core-moos through 10.4.0 fails to validate client identity in MOOSDB message processing, allowing authenticated attackers to attribute writes to other clients by supplying arbitrary source identifiers in serialized messages. Attackers can forge message origins and cancel third-party subscriptions by exploiting the disconnect between authenticated connection identity and wire-supplied source attribution.
Affected products
themoos: core-moos
References5
- github.com/themoos/core-moos/commit/26308f0e393f0e80bfa09b27589… Issue TrackingPatch
- github.com/themoos/core-moos/pull/76 Issue TrackingPatch
- github.com/themoos/core-moos Product
- github.com/themoos/core-moos/blob/ec9c77c68fcbdef8f5e4c60fe243a… Issue Tracking
- www.vulncheck.com/advisories/moos-core-moos-through-10.4.0-moos… Third Party Advisory
Metrics
- CVSS 3.1
-
8.2
HIGH
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L - CVSS 4.0
-
8.8
HIGH
Score source: CNA
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X - EPSS — exploit probability
- 1% percentile: 43 · as of 2 November 2026
- CWE
- CWE-290
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.