MOOS core-moos through 10.4.0 MOOSDB Message Source Spoofing via Wire Identity
Published Sep 3, 2026 · Updated Nov 3, 2026
Original summary
Normalized public record · Updated Nov 3, 2026
MOOS core-moos through 10.4.0 MOOSDB Message Source Spoofing via Wire Identity
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
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.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- MEDIUM
- Confidence
- Not available
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
- GitHub advisory ↗
- Patch commit ↗
- Source repository ↗
- Source repository ↗
- VulnCheck Advisory: MOOS core-moos through 10.4.0 MOOSDB Message Source Spoofing via Wire Identity ↗
Record history
Published Sep 3, 2026 · Last refreshed Nov 3, 2026