CVE-2025-41759 json
Use of wildcard (“*” or “all”) in Block list
published 2026-03-09 8 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-208364
- cvss
- 4.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 30%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- MBS UBR-01 Mk II 6.0.1.0
- MBS UBR-02 6.0.1.0
- MBS UBR-LON 6.0.1.0
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 8 mo ago
Exploit prediction
0.36% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N |
Affected products
- MBS UBR-01 Mk II
- MBS UBR-02
- MBS UBR-LON
Classification
- Weakness
-
- CWE-636 Not Failing Securely
References
-
mbs-solutions.de
/mbs-2025-0001
vendor-advisory
Sources
- CVE List CVE-2025-41759
- NVD CVE-2025-41759
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.