dbcve.org
Universal Gateway FirmwareOperating system · Mbs Solutions

CVE-2026-35080

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-restoreinfo 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

A path traversal vulnerability in the ugw-restoreinfo method allows any authenticated remote user to delete arbitrary files on the local system due to insufficient validation of user-controlled input used in file path construction.

MitigationImplement strict allowlist-based input validation and canonicalize file paths to prevent directory traversal before using them in file deletion operations.

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 firmware version
    Check the installed Mbs Solutions Universal Gateway Firmware version through the system info panel, CLI command, or firmware metadata file. Compare this version against the affected range of < 6_00_07.
    Affected if The installed firmware version is any version lower than 6_00_07.
  2. Locate the ugw-restoreinfo method
    Search the application filesystem for the ugw-restoreinfo method, handler, or endpoint definition. This may be in the web application routing configuration, API definitions, or application source code directories.
    Affected if The ugw-restoreinfo method exists and is present in the deployed application.
  3. Verify method accessibility
    Determine whether the ugw-restoreinfo method is exposed via the web interface, API, or CLI. Check the access control configuration, routing rules, or method visibility settings.
    Affected if The method is accessible without proper authentication or authorization controls.
  4. Inspect path parameter handling
    Examine the source code or configuration of the ugw-restoreinfo method to see how path parameters are processed. Look for direct use of user-supplied input in file deletion operations without sanitization or validation.
    Affected if The method accepts path parameters and uses them directly in file operations without validation or path normalization.
  5. Review input validation configuration
    Check if there are any allowlist validation rules, path normalization settings, or directory restriction configurations applied to the ugw-restoreinfo method or the broader file operation subsystem.
    Affected if No strict input validation, path allowlisting, or directory restrictions are configured for file deletion operations.

A user is affected if running firmware version lower than 6_00_07 with the ugw-restoreinfo method exposed and lacking proper input validation on path parameters.

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 allowlist-based input validation and canonicalize file paths to prevent directory traversal before using them in file deletion operations.

Recommended fix High confidence

Universal Gateway Firmware version 6_00_07

  1. 1. Identify all Universal Gateway devices running firmware versions prior to 6_00_07
  2. 2. Access the device management interface and navigate to the firmware version check (typically in System > Firmware or Administration > Software Update)
  3. 3. Download the firmware version 6_00_07 or later from the vendor's official support portal
  4. 4. Initiate the firmware upgrade process following the vendor's documented upgrade procedure
  5. 5. After reboot, verify the new firmware version is 6_00_07 or higher
  6. 6. Test the ugw-restoreinfo functionality to confirm the fix is working properly

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-35080 — 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-35080 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