The ugw-logstop method allows a remote attacker with user privileges to terminate arbitrary…
CVE-2026-35081 is a high-severity improper input validation vulnerability in Single-A from MBS, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists version V6_00_07 as the first without the flaw, so updating Single-A to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.37% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Single-A to V6_00_07 or a later version.
- Update Double-A Profibus to V6_00_07 or a later version.
- Update Double-A x-link to V6_00_07 or a later version.
- Read the advisory on certvde.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| MBS | Single-A | V1_00_00 up to, but not including, V6_00_07 | V6_00_07 |
| MBS | Double-A Profibus | V1_00_00 up to, but not including, V6_00_07 | V6_00_07 |
| MBS | Double-A x-link | V1_00_00 up to, but not including, V6_00_07 | V6_00_07 |
| MBS | Single-X | V1_00_00 up to, but not including, V6_00_07 | V6_00_07 |
| MBS | Double-X CAN | V1_00_00 up to, but not including, V6_00_07 | V6_00_07 |
| MBS | Double-X DALI | V1_00_00 up to, but not including, V6_00_07 | V6_00_07 |
| MBS | Double-X KNX | V1_00_00 up to, but not including, V6_00_07 | V6_00_07 |
| MBS | Double-X LON | V1_00_00 up to, but not including, V6_00_07 | V6_00_07 |
| MBS | Double-X M-Bus | V1_00_00 up to, but not including, V6_00_07 | V6_00_07 |
| MBS | Double-X PROFINET | V1_00_00 up to, but not including, V6_00_07 | V6_00_07 |
| MBS | Double-X x-link | V1_00_00 up to, but not including, V6_00_07 | V6_00_07 |
| MBS | Triple-X KNX+DALI | V1_00_00 up to, but not including, V6_00_07 | V6_00_07 |
| MBS | Triple-X KNX+LON | V1_00_00 up to, but not including, V6_00_07 | V6_00_07 |
| MBS | Triple-X KNX+M-Bus | V1_00_00 up to, but not including, V6_00_07 | V6_00_07 |
| MBS | Triple-X PROFINET+DALI | V1_00_00 up to, but not including, V6_00_07 | V6_00_07 |
| MBS | Triple-X PROFINET+KNX | V1_00_00 up to, but not including, V6_00_07 | V6_00_07 |
| MBS | Triple-X PROFINET+LON | V1_00_00 up to, but not including, V6_00_07 | V6_00_07 |
| MBS | Triple-X PROFINET+M-Bus | V1_00_00 up to, but not including, V6_00_07 | V6_00_07 |
| Mbs-solutions | Universal Gateway Firmware | before 6_00_07 | 6_00_07 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H. Scored by CNA (cert.vde.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 7.2 | High | CNA (cert.vde.com) |
| CVSS 3.1 | 8.1 | High | CNA (cert.vde.com) |
Official description
The ugw-logstop method allows a remote attacker with user privileges to terminate arbitrary processes due to insufficient validation of user-supplied input.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Input Validation
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
How developers prevent this class of flaw
- Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build recognizers for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses.
- Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
- Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other vulnerabilities in Single-A
- 8.8 High severity
- 8.1 High severity
- 8.1 High severity
- 8.1 High severity
- 8.1 High severity
- 8.1 High severity
Recent Improper Input Validation vulnerabilities
- 9.1 Critical severity
- 7.5 High severity
- 7.5 High severity
- 8.1 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.