CVE-2025-28386: n/a
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 1.0% chance of exploitation in 30 days – higher than 64% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 13 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
1. Immediate Inventory and Assessment: Identify all instances of OpenC3 COSMOS v6.0.0 within the organization, focusing on those with active Plugin Management components. 2. Restrict File Upload Capabilities: Temporarily disable or restrict the Plugin Management file upload functionality to trusted users only, or suspend plugin uploads until a patch is available. 3. Network Segmentation: Isolate systems running OpenC3 COSMOS from general enterprise networks to limit exposure and lateral movement in case of compromise. 4. Implement Application Whitelisting: Enforce strict execution policies to prevent unauthorized code execution from unexpected files or directories. 5. Monitor and Log File Uploads: Enable detailed logging of file upload activities and monitor for unusual or unauthorized upload attempts, especially involving .txt files. 6. Engage with Vendor: Contact OpenC3 COSMOS vendor or support channels to obtain patches or official mitigation guidance as soon as they become available. 7. Prepare Incident Response: Develop and rehearse incident response plans specific to potential exploitation scenarios involving OpenC3 COSMOS. 8. Employ Intrusion Detection: Deploy host-based and network-based intrusion detection systems with signatures or heuristics targeting suspicious file upload and execution behaviors. These measures go beyond generic advice by focusing on the unique aspects of the Plugin Management component and the operational context of OpenC3 COSMOS.
Description
A remote code execution (RCE) vulnerability in the Plugin Management component of OpenC3 COSMOS v6.0.0 allows attackers to execute arbitrary code via uploading a crafted .txt file.