dbcve.org
Universal Gateway FirmwareOperating system · Mbs Solutions

CVE-2026-35084

HIGH · 8.8 CVSS v3.1 Published 2026-06-03
Fix available
A fix is available. Upgrade to 6_00_07 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 remote attacker with user privileges can exploit a stack buffer overflow in dali-devconfig to gain full system access as root.

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 buffer overflow vulnerability in dali-devconfig allows an authenticated remote attacker to overflow a stack-allocated buffer and execute arbitrary code with root privileges, achieving full system compromise.

MitigationRestrict network access to dali-devconfig, implement strict input validation on all user-controlled data entering the vulnerable buffer, and apply vendor security patches when available.

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 Gateway FirmwareOperating system
Affected:< 6_00_07

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 product
    Check the system or web interface for the product name - look for 'Mbs Solutions Universal Gateway' or check /proc/cpuinfo, /etc/version, or the device web UI for product identification
    Affected if The device is NOT the Mbs Solutions Universal Gateway - different products are not affected by this specific CVE
  2. Check the installed firmware version
    Access the device management interface, check system info page, or use CLI command like 'version', 'show version', or check /etc/firmware_version if available
    Affected if The firmware version is any version below 6_00_07 (e.g., 6_00_06, 5_xx_xx, etc.) - versions prior to 6_00_07 contain the vulnerable code
  3. Verify dali-devconfig utility presence and exposure
    Check if the dali-devconfig binary exists on the system - look in /usr/bin/, /sbin/, or similar directories; check if the service is listening on network ports using 'netstat -tulpn' or 'ss -tulpn'
    Affected if dali-devconfig is present AND exposed on a network interface - the vulnerability requires this specific utility to be accessible
  4. Assess authentication and user access
    Review user accounts configured on the device - check /etc/passwd, user management UI, or authentication logs to determine if non-privileged user accounts exist
    Affected if There are authenticated user accounts with any privilege level - the CVE states an attacker needs 'existing user privileges' to exploit this flaw

The environment is affected only if the device is a Mbs Solutions Universal Gateway running firmware version below 6_00_07 with dali-devconfig accessible to authenticated users on the network.

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_00_07 or later
Fixed in 6_00_07
Interim mitigation

Restrict network access to dali-devconfig, implement strict input validation on all user-controlled data entering the vulnerable buffer, and apply vendor security patches when available.

Recommended fix High confidence

Universal Gateway Firmware version 6_00_07

  1. 1. Obtain the Universal Gateway Firmware version 6_00_07 from the vendor's official support portal or download center
  2. 2. Access the device administration interface or console
  3. 3. Navigate to the firmware update or system upgrade section
  4. 4. Upload the firmware version 6_00_07 file
  5. 5. Apply the firmware update and wait for the device to reboot
  6. 6. Verify the firmware version has been successfully updated to 6_00_07
  7. 7. Confirm the dali-devconfig component is no longer vulnerable by testing or reviewing release notes
Caveat Firmware upgrades may introduce compatibility changes; review vendor release notes before applying in production environments

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

Fix this in Universal Gateway Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-35084 — 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-2026-35084 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