CVE-2025-28389VulnerabilityPublished 13 Jun 2025

CVE-2025-28389: n/a

Source CVE Database V5

Not known to be exploited.

Data as of 25 Oct 2026, 19:02 UTC

Severity

High

Rated High by the CNA (mitre) · No CVSS score from NVD or the CNA

EPSS: 0.5% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation 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 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

1. Immediately review and strengthen password policies within OpenC3 COSMOS environments, enforcing minimum complexity, length, and lockout thresholds to prevent brute force attempts. 2. Implement account lockout mechanisms after a defined number of failed login attempts to slow or block brute force attacks. 3. Deploy multi-factor authentication (MFA) to add an additional layer of security beyond passwords. 4. Monitor authentication logs for unusual login attempts or patterns indicative of brute force activity and establish alerting mechanisms. 5. Restrict network access to authentication interfaces using network segmentation, firewalls, and VPNs to limit exposure to untrusted networks. 6. Regularly update and patch OpenC3 COSMOS as vendor fixes become available. 7. Conduct penetration testing and security assessments focused on authentication mechanisms to identify and remediate weaknesses. 8. Educate system administrators and users about the risks of weak passwords and the importance of secure authentication practices. 9. If possible, implement intrusion prevention systems (IPS) or web application firewalls (WAF) that can detect and block brute force attempts at the network perimeter.

Description

Weak password requirements in OpenC3 COSMOS v6.0.0 allow attackers to bypass authentication via a brute force attack.

Impact

For European organizations, especially those operating critical infrastructure, industrial control systems, or command and control platforms using OpenC3 COSMOS, this vulnerability poses a significant risk. Unauthorized access could lead to data breaches, manipulation of operational parameters, or disruption of essential services. The ability to bypass authentication through brute force attacks means that attackers can gain persistent access, potentially leading to espionage, sabotage, or ransomware deployment. Given the strategic importance of sectors such as energy, transportation, and manufacturing in Europe, exploitation could have cascading effects on national security and economic stability. Additionally, organizations subject to strict data protection regulations like GDPR may face compliance violations and reputational damage if breaches occur. The lack of known exploits currently provides a window for proactive defense, but the simplicity of the attack vector increases the likelihood of future exploitation. The impact is heightened in environments where multi-factor authentication or additional access controls are not implemented, as the weak password policy alone becomes the single point of failure.

References

Community reviews

Loading reviews…