CVE-2026-85432

Received Received - Intake

MOOSDB Message Origin Spoofing in MOOS core-moos

Publication date: 2026-09-03

Last updated on: 2026-09-03

Assigner: VulnCheck

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-09-03

Last Modified

2026-09-03

Generated

2026-09-04

AI Q&A

2026-09-04

EPSS Evaluated

N/A

NVD

CVE-2026-85432

Affected Vendors & Products

Vendor	Product	Version / Range
moos	core_moos	to 10.4.0 (inc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-290	This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.

Attack-Flow Graph

Executive Summary

MOOS core-moos through 10.4.0 does not verify client identity when processing MOOSDB messages. Authenticated attackers can send messages with fake source identifiers, making writes appear to come from other clients. This allows forgery of message origins and cancellation of third-party subscriptions by exploiting the mismatch between authenticated connections and wire-supplied source attribution.

Detection Guidance

This vulnerability involves forged message origins in MOOS core-moos through 10.4.0. Detection requires monitoring for messages with inconsistent source identifiers or unexpected client behavior. Check MOOSDB logs for messages with mismatched authenticated identities and wire-supplied source fields. Use network monitoring tools to inspect MOOS protocol traffic for irregular message patterns.

Impact Analysis

An attacker could impersonate other users or systems, leading to unauthorized data manipulation or service disruption. They might cancel legitimate subscriptions, causing missed updates or system failures. The impact includes data integrity issues and potential denial of service due to forged messages.

Compliance Impact

This vulnerability could violate compliance requirements that mandate data integrity, non-repudiation, and secure authentication. GDPR requires data protection and accountability, while HIPAA demands integrity controls for health data. Forged messages may lead to unauthorized access or data tampering, risking non-compliance.

Mitigation Strategies

Update MOOS core-moos to the latest version beyond 10.4.0 to ensure proper client identity validation in MOOSDB message processing. Review and restrict network access to MOOSDB to trusted sources only.

Hi! I’m here to help you understand CVE-2026-85432. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70