Skip to main content
VulnerabilityPublished

CVE-2025-41766: MBS UBR-01 Mk II · Out-of-bounds Write

Affects MBS UBR-01 Mk IISource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 6.0.1.0 soon.

Data as of 30 Oct 2026, 06:59 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 29 Oct 2026.

What to do

Upgrade UBR-01 Mk II and UBR-02 and UBR-LON to 6.0.1.0.

Affected software

ProductAffectedFixed in
MBSUBR-01 Mk IIAffected
  • <6.0.1.0
Fixed in
  • 6.0.1.0
MBSUBR-02Affected
  • <6.0.1.0
Fixed in
  • 6.0.1.0
MBSUBR-LONAffected
  • <6.0.1.0
Fixed in
  • 6.0.1.0

AI-suggested

Organizations should immediately inventory their network infrastructure to identify any MBS UBR-01 Mk II devices. If you cannot patch yet, network segmentation should be enforced to isolate these devices from untrusted networks. Implement strict ingress filtering and firewall rules to restrict access to the device management interfaces, especially blocking HTTP POST requests using the ubr-network method from untrusted sources. Monitor network traffic for anomalous POST requests targeting the device. Employ intrusion detection/prevention systems (IDS/IPS) with custom signatures to detect attempts to exploit this buffer overflow. Limit privileges of accounts that can access the device remotely and enforce strong authentication mechanisms. Additionally, consider deploying network behavior anomaly detection tools to identify unusual device behavior indicative of compromise. Regular backups of device configurations should be maintained to enable rapid recovery if compromise occurs.

Description

A low-privileged remote attacker can trigger a stack-based buffer overflow via a crafted HTTP POST request using the ubr-network method resulting in full device compromise.

References

Community reviews

Loading reviews…