CVE-2025-41759
An administrator may attempt to block all networks by specifying "\*" or "all" as the network identifier.
Published Mar 9, 2026 · updated Jun 17, 2026 · mbs-solutions universal bacnet router firmware
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.
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Mar 9, 2026 · NIST NVD
Detected
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.
Jun 17, 2026 · NIST NVD
Updated
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
- cpe mbs-solutions/universal bacnet router firmwareversion unspecified
Sources
- NIST NVDVulnerability recordCVE-2025-41759
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 blocke
nvd.nist.gov