dbcve.org
Universal Gateway FirmwareOperating system · Mbs Solutions

CVE-2026-35079

HIGH · 8.1 CVSS v3.1 Published 2026-06-03
Fix available
A fix is available. Upgrade to 6_00_07 or later.
See remediation →
87/100
Remediation priority · High
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
The ugw-restore method allows a remote attacker with user privileges to delete arbitrary local files due to insufficient validation of user-controlled input.

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

The ugw-restore method in an unspecified product permits authenticated remote users to delete arbitrary local files due to insufficient validation of user-controlled input, likely a path traversal vulnerability.

MitigationImplement strict input validation and path sanitization in the ugw-restore method to ensure only authorized files within allowed directories can be deleted.

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
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 product and firmware version
    Access the web interface or CLI and locate the firmware version information for Mbs Solutions Universal Gateway. This is typically found in System > Status, System > About, or via CLI command 'show version' or 'system info'.
    Affected if The installed firmware version is Universal Gateway Firmware and is lower than 6_00_07
  2. Verify ugw-restore method is accessible
    Check if the ugw-restore functionality exists in the application. This may be accessible via web API endpoint, administrative interface, or CLI restore command. Look for restore/backup functions in the web interface or API routes.
    Affected if The ugw-restore method exists and is exposed for use
  3. Confirm user authentication is enabled
    Verify that authentication is required to access the ugw-restore functionality. Check if the system allows standard privileged users to authenticate and access restore features without elevated admin rights.
    Affected if Standard authenticated users (non-admin) can access the restore function
  4. Check authorization controls on restore function
    Inspect the access control configuration or user role permissions to determine if standard users have permission to execute restore operations that can specify file paths.
    Affected if Standard users have delete/write permissions through the restore function without proper path validation enforced

A user is affected if they are running Mbs Solutions Universal Gateway Firmware version below 6_00_07 with the ugw-restore method accessible to authenticated standard-privilege users.

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

Implement strict input validation and path sanitization in the ugw-restore method to ensure only authorized files within allowed directories can be deleted.

Recommended fix Moderate confidence

Universal Gateway Firmware version 6_00_07

  1. Obtain the Universal Gateway Firmware version 6_00_07 from the official vendor source (www.certvde.com reference indicates Cert VDE is the vendor)
  2. Review the vendor's firmware upgrade documentation specific to the Universal Gateway device
  3. Backup the current device configuration before initiating the upgrade
  4. Upload and apply firmware version 6_00_07 to the Universal Gateway device using the vendor's recommended procedure
  5. Verify the upgrade completed successfully and confirm the ugw-restore method now properly validates input

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

Fix this in Universal Gateway Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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