dbcve.org
Universal Bacnet Router FirmwareOperating system · Mbs Solutions

CVE-2025-41766

HIGH · 8.8 CVSS v3.1 Published 2026-03-09
Fix available
A fix is available. Upgrade to 6.0.1.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A low-privileged remote attacker can trigger a stack-based buffer overflow via a crafted HTTP POST request using the ubr-network method resulting in full device compromise.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A stack-based buffer overflow vulnerability exists in the ubr-network method of the target device. A low-privileged remote attacker can exploit this by sending a crafted HTTP POST request with oversized data, overwriting stack memory and executing arbitrary code to achieve full device compromise.

MitigationImplement strict bounds checking on all input accepted by the ubr-network HTTP POST handler to prevent buffer overflows, and apply any available vendor patches for this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Universal Bacnet Router FirmwareOperating system
Affected:< 6.0.1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the device web interface or CLI and confirm the product is Mbs Solutions Universal Bacnet Router. Check the device status page or system information for the exact model name.
    Affected if The device is not an Mbs Solutions Universal Bacnet Router, skip this CVE check.
  2. Determine the installed firmware version
    Navigate to the device firmware/version settings in the web UI or run the appropriate CLI command (such as 'show version' or 'system info') to retrieve the current firmware build number.
    Affected if The installed firmware version is below 6.0.1.0, indicating the device falls within the affected version range.
  3. Verify the ubr-network service is enabled
    Access the device network settings or service configuration page. Look for the 'ubr-network' service, HTTP server settings, or Bacnet router service status. Confirm whether this HTTP POST handler is actively enabled.
    Affected if The ubr-network HTTP POST handler is enabled on the device, making the overflow vulnerability accessible.
  4. Check network exposure of the HTTP service
    Review the device network configuration for HTTP/HTTPS service bindings. Determine if the web interface is bound to WAN/outside interfaces or is accessible from untrusted networks. Use port scanning from an external location or review firewall rules.
    Affected if The ubr-network HTTP service is exposed to untrusted networks (WAN, DMZ, or accessible without authentication from outside the local network).

The environment is affected if it is an Mbs Solutions Universal Bacnet Router running firmware version below 6.0.1.0 with the ubr-network HTTP POST handler enabled and accessible to remote attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.0.1.0 or later
Fixed in 6.0.1.0
Interim mitigation

Implement strict bounds checking on all input accepted by the ubr-network HTTP POST handler to prevent buffer overflows, and apply any available vendor patches for this vulnerability.

Recommended fix High confidence

Universal Bacnet Router Firmware version 6.0.1.0

  1. Identify the current firmware version of the Universal Bacnet Router device
  2. Download firmware version 6.0.1.0 or later from the vendor (MBS-Solutions)
  3. Consult device documentation for the specific firmware upgrade procedure (typically via web interface, TFTP, or USB)
  4. Apply the firmware update following vendor-provided instructions
  5. Verify the firmware has been successfully updated to version 6.0.1.0 or later
  6. Confirm the ubr-network HTTP POST endpoint no longer exhibits the buffer overflow vulnerability

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Universal Bacnet Router Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,180
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-41766 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-41766 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data