Skip to main content
CVE-2025-41688VulnerabilityPublished

CVE-2025-41688: MB connect line mbNET HW1 · Improper Isolation or Compartmentalization

Affects MB connect line mbNET HW1Source CVE Database V5

0

Not known to be exploited · CVSS 7.2 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Jul 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 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
MB connect line mbNET HW1Affected
  • =0.0.0
Fixed in–

AI-suggested

Since no patches are currently available, European organizations should implement immediate compensating controls. These include: 1) Restricting network access to mbNET HW1 devices by implementing strict firewall rules and network segmentation to limit exposure to trusted management networks only. 2) Enforcing strong authentication and access controls to ensure that only authorized personnel with necessary privileges can access the device interfaces. 3) Monitoring device logs and network traffic for unusual activities that may indicate attempts to exploit the undocumented method. 4) Disabling or restricting LUA scripting capabilities if possible, or applying configuration changes to limit script execution scope. 5) Engaging with MB connect line support for any available workarounds or upcoming patches and planning for timely updates once patches are released. 6) Conducting thorough risk assessments on the use of mbNET HW1 devices within critical environments and considering alternative solutions if risk tolerance is low. 7) Enhancing incident response readiness to quickly detect and respond to potential exploitation attempts.

Description

A high privileged remote attacker can execute arbitrary OS commands using an undocumented method allowing to escape the implemented LUA sandbox.

References

Community reviews

Loading reviews…