Skip to content
Connect AISign inSign up free
CVE-2025-417594.9MediumCWE-636

CVE-2025-41759: Use of wildcard (“*” or “all”) in Block list

MBS · UBR-01 Mk II

Vendor fix available · Affected: MBS UBR-01 Mk II · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.4%probability of exploitation in the next 30 days
30th percentile
050100

Higher than 30% of scored CVEs

4.9MediumCVSS 3.1
LowMedium

DescriptionCVE.org

An administrator may attempt to block all networks by specifying "\*" or "all" as the network identifier. However, these values are not supported and do not trigger any validation error. Instead, they are silently interpreted as network 0 which results in no networks being blocked at all.

Affected products3

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • MBS · UBR-01 Mk IIfrom 0.0.0 before 6.0.1.0
  • MBS · UBR-02from 0.0.0 before 6.0.1.0
  • MBS · UBR-LONfrom 0.0.0 before 6.0.1.0

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV
Not listed
Public check
No public nuclei template
Vendor
MBS
Published
March 2026

CoverageNo articles yet

No CyberSIXT article names CVE-2025-41759 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References