CVE-2026-35079: Arbitrary file delete vulnerability in method ugw-restore
The ugw-restore method allows a remote attacker with user privileges to delete arbitrary local files due to insufficient validation of user-controlled input.
Metrics
- CVSS v4.0
- 7.2
- Severity
- HIGH
- Fixed in
- V6_0_0_7
- Affected Products
- 18
HarborGuard Analysis
Synopsis
An arbitrary file deletion vulnerability affects the ugw-restore method in multiple MBS gateway device variants (Single-A, Double-A Profibus, Double-A x-link, Single-X, Double-X CAN, Double-X DALI, Double-X KNX, and Double-X LON) running firmware versions prior to V6_0_0_7. The flaw is reachable over the network by any authenticated user with low-privilege credentials, requiring no interaction from another user or administrator. Successful exploitation lets an attacker delete arbitrary files on the local filesystem, which can corrupt device configuration, destroy stored data, or bring down the affected service. A patched-image rebuild at V6_0_0_7 is available on HarborGuard for affected environments.
HarborGuard Coverage
Detection of CVE-2026-35079 is available across every HarborGuard environment: the CVE is ingested from upstream advisory feeds within minutes of publication and matched against images in customer registries and CI/CD pipelines, including custom-built images that bundle MBS firmware or dependent components.
AvailableHarborGuard is capable of scoring this CVE at its CVSS v4.0 rating of 7.2 (HIGH) and weighting that score against each environment's compliance policy to surface it at the correct priority level; automated routing then delivers the finding to the appropriate team inbox within the customer organization.
AvailableA patched-image rebuild at firmware version V6_0_0_7 becomes available on HarborGuard for any environment where an affected version is detected. For customers who opt into auto-remediation, the platform performs a rebuild, runs a regression test suite, and opens a pull request against affected workloads automatically.
AvailableExploit Conditions
- Network reachabilityRequired
The attacker must reach the ugw-restore endpoint over the network; the service must be exposed to the attacker's network segment.
- AuthenticationRequired
Any low-privilege user account is sufficient; no administrative or elevated permissions are needed beyond basic authenticated access.
- Victim interactionNot required
The attacker can trigger the vulnerability directly without any action from another user or an administrator.
- Attack complexityDetail
The exploit is reliable and condition-free, requiring no race conditions, special memory layout, or environmental prerequisites.
Blast Radius
- An attacker can delete arbitrary files on the device filesystem, including configuration files, credentials stores, and runtime state.
- Deletion of critical system files disrupts or crashes the affected MBS gateway service, causing loss of availability for connected industrial or building-automation processes.
- Targeted deletion of configuration or firmware files can leave the device in an unrecoverable or degraded state, requiring physical intervention to restore.
How HarborGuard Handles This
Available on HarborGuard: detection for CVE-2026-35079 is active across customer registries and pipelines at the moment of ingestion, with triage scored at 7.2 HIGH and routed according to each environment's compliance policy. Where compliance policy permits auto-remediation, HarborGuard can rebuild affected images at the patched version V6_0_0_7, run regression tests against the rebuilt image, and open a pull request against affected workloads; for high-severity issues, median time from CVE publication to merged patch PR in environments with auto-remediation enabled is around 90 minutes. Customers who manage remediation manually will find the patched rebuild staged and ready in their HarborGuard dashboard for promotion at their discretion.
Fix available
- MBS / Single-A< V6_0_0_7 (from V1_0_0_0)
- MBS / Double-A Profibus< V6_0_0_7 (from V1_0_0_0)
- MBS / Double-A x-link< V6_0_0_7 (from V1_0_0_0)
- MBS / Single-X< V6_0_0_7 (from V1_0_0_0)
- MBS / Double-X CAN< V6_0_0_7 (from V1_0_0_0)
- MBS / Double-X DALI< V6_0_0_7 (from V1_0_0_0)
- MBS / Double-X KNX< V6_0_0_7 (from V1_0_0_0)
- MBS / Double-X LON< V6_0_0_7 (from V1_0_0_0)
- MBS / Double-X M-Bus< V6_0_0_7 (from V1_0_0_0)
- MBS / Double-X PROFINET< V6_0_0_7 (from V1_0_0_0)
- MBS / Double-X x-link< V6_0_0_7 (from V1_0_0_0)
- MBS / Triple-X KNX+DALI< V6_0_0_7 (from V1_0_0_0)
- MBS / Triple-X KNX+LON< V6_0_0_7 (from V1_0_0_0)
- MBS / Triple-X KNX+M-Bus< V6_0_0_7 (from V1_0_0_0)
- MBS / Triple-X PROFINET+DALI< V6_0_0_7 (from V1_0_0_0)
- MBS / Triple-X PROFINET+KNX< V6_0_0_7 (from V1_0_0_0)
- MBS / Triple-X PROFINET+LON< V6_0_0_7 (from V1_0_0_0)
- MBS / Triple-X PROFINET+M-Bus< V6_0_0_7 (from V1_0_0_0)
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N