A vulnerability was detected in Cobham SATCOM VSAT7090 Maritime Satellite Router up to 20260704. This issue affects the function c_set_reports_decode of the file mail-report.sh of the component JSON Parsing. The manipulation of the argument sender/recipients results in command injection. It is possible to launch the attack remotely. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
Security readout for executives and security teams
Plain-English summary
A remotely reachable flaw in the Cobham SATCOM VSAT7090 can let a low-privileged authenticated attacker turn mail-report sender or recipient data into operating-system commands. Successful exploitation could expose information, alter router behavior, or disrupt service. The supplied sources identify public exploit material but do not establish attacks in the wild.
Executive priority
Prioritize immediate exposure assessment and containment for reachable VSAT7090 routers, especially operationally critical maritime deployments. Public exploit material and potential full-system impact justify urgent action. Coordinate firmware decisions with the vendor and operations teams because the supplied sources provide no confirmed patch or vendor mitigation.
Technical view
The c_set_reports_decode function in mail-report.sh reportedly passes attacker-controlled JSON sender or recipients values into a command context without adequate neutralization. The CVSS 3.1 assessment is 9.9: network-accessible, low complexity, low privileges, no user interaction, changed scope, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is highest where a VSAT7090 running version 20260704 or earlier permits untrusted network access to the affected JSON configuration function. Authentication is reportedly required, but only low privileges. The supplied sources do not identify default reachability, affected configurations, or deployment prevalence.
Exploitation context
Public exploit material is referenced, so practical reproduction may be easier. However, this CVE is not identified as CISA KEV in the supplied bundle, and no cited source confirms active exploitation. Treat public availability as elevated likelihood, not evidence of compromise.
Researcher notes
The classification aligns with CWE-74 and CWE-77. Evidence is primarily a VulDB disclosure and linked submission; the vendor reportedly did not respond. Important unknowns include the exact endpoint, required role, firmware lineage, default exposure, command execution identity, reliable indicators, and remediation status. Avoid interpreting public exploit availability as confirmed exploitation.
Mitigation direction
Check Cobham guidance and obtain supported fixed firmware; the supplied sources name no patch.
Restrict router management and API access to trusted administrative networks and authorized VPN users.
Disable mail-report functionality if unnecessary and operationally safe.
Review low-privileged accounts and revoke access that is not required.
Monitor changes to sender and recipient settings for suspicious input.
Validation and detection
Inventory VSAT7090 devices and confirm firmware versions, including version 20260704 or earlier.
Determine whether untrusted networks or low-privileged accounts can reach the affected JSON function.
Review relevant access, configuration, and system logs for anomalous sender or recipient changes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-74: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
4CVSS vectors
6Timeline events
1ADP providers
6Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
4 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-74 · source CWE mapping
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Neutralization of Special Elements used in a Command ('Command Injection')
Improper Neutralization of Special Elements used in a Command ('Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.