Skip to main content
VulnerabilityPublished

CVE-2025-3090: MB connect line mbCONNECT24 · Missing Authentication

Affects MB connect line mbCONNECT24Source CVE Database V5

0

Not known to be exploited · CVSS 8.2 High.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% 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:L/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

Affected software

ProductAffectedFixed in
MB connect line mbCONNECT24Affected
  • =0
Fixed in–

AI-suggested

1. Immediate network-level protections: Restrict access to mbCONNECT24 devices by implementing strict firewall rules and network segmentation to limit exposure to untrusted networks, especially the internet. 2. Deploy VPNs or secure tunnels for remote access to ensure authentication and encryption at the network layer. 3. Monitor network traffic for unusual patterns or repeated access attempts targeting mbCONNECT24 devices to detect potential exploitation attempts early. 4. Engage with MB connect line for official patches or firmware updates addressing this vulnerability; if unavailable, consider temporary device isolation or replacement. 5. Implement compensating controls such as intrusion detection/prevention systems (IDS/IPS) tailored to detect exploitation attempts of this specific vulnerability. 6. Conduct thorough asset inventories to identify all mbCONNECT24 instances and prioritize remediation based on criticality. 7. Educate operational technology and IT teams about this vulnerability to ensure rapid response and incident handling.

Description

An unauthenticated remote attacker can obtain limited sensitive information and/or DoS the device due to missing authentication for critical function.

References

Community reviews

Loading reviews…