CVE-2025-41764: MBS UBR-01 Mk II · Missing Authorization
Affects MBS UBR-01 Mk IISource CVE Database V5
Not known to be exploited · CVSS 9.1 Critical : upgrade to 6.0.1.0 as a priority.
Data as of 30 Oct 2026, 11:52 UTC
Contested
Critical score, yet low EPSS after six months- EPSS
- 0.4% chance of exploitation in 30 days – higher than 36% 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:N/UI:N/S:U/C:N/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 9 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 Oct 2026.
What to do
Upgrade UBR-01 Mk II and UBR-02 and UBR-LON to 6.0.1.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| MBSUBR-01 Mk II | Affected
| Fixed in
|
| MBSUBR-02 | Affected
| Fixed in
|
| MBSUBR-LON | Affected
| Fixed in
|
AI-suggested
To mitigate CVE-2025-41764, organizations should implement the following specific measures: 1) Immediately restrict network access to the wwwupdate.cgi endpoint by applying firewall rules or access control lists to limit update interface exposure only to trusted management networks or IP addresses. 2) Employ network segmentation to isolate affected devices from general user or internet-facing networks to reduce attack surface. 3) Monitor network traffic and device logs for any unauthorized or anomalous update attempts or unusual activity on the update endpoint. 5) If patches are unavailable, consider disabling remote update functionality temporarily or implementing manual update procedures with strict physical or network controls. 6) Conduct regular security audits and penetration tests focusing on device management interfaces to detect similar authorization weaknesses. 7) Educate network administrators about the risk and ensure secure configuration management practices are followed. These steps go beyond generic advice by focusing on access restriction, monitoring, and vendor engagement specific to this vulnerability’s vector.
Description
Due to insufficient authorization enforcement, an unauthorized remote attacker can exploit the wwwupdate.cgi endpoint to upload and apply arbitrary updates.