MOOS-IvP through 24.8.1 iSay Command Injection via SAY_MOOS
Published Sep 3, 2026 · Updated Nov 3, 2026
Original summary
Normalized public record · Updated Nov 3, 2026
MOOS-IvP through 24.8.1 iSay Command Injection via SAY_MOOS
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
MOOS-IvP iSay through 24.8.1 contains a remote code execution vulnerability in the SAY_MOOS variable handler that passes unsanitized text to a shell command. Attackers can publish SAY_MOOS messages containing backticks or command substitution syntax to execute arbitrary commands as the iSay process user.
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-IvP through 24.8.1 iSay Command Injection via SAY_MOOS ↗
Record history
Published Sep 3, 2026 · Last refreshed Nov 3, 2026