Legion Zone Application: Deserialization of Untrusted Data
CVE-2026-75941 is a high-severity deserialization of untrusted data vulnerability in Legion Zone Application from Lenovo, with a CVSS 3.1 base score of 8.0 out of 10. It can be exploited from the same local network by an attacker with a low-privileged account, without any action from a user. The record lists version 2.0.28.8182 as the first without the flaw, so updating Legion Zone Application to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.26% 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 Legion Zone Application to 2.0.28.8182 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Lenovo | Legion Zone Application | before 2.0.28.8182 | 2.0.28.8182 |
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
- AdjacentThe attacker must be on the same local network segment.
- 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
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (lenovo.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 8.6 | High | CNA (lenovo.com) |
| CVSS 3.1 | 8.0 | High | CNA (lenovo.com) |
Official description
A potential vulnerability was reported in the Lenovo Legion Zone application, distributed exclusively in the Chinese market, that could allow an attacker on the same logical network to execute arbitrary code.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Deserialization of Untrusted Data
The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
How developers prevent this class of flaw
- If available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.
- When deserializing data, populate a new object rather than just deserializing. The result is that the data flows through safe input validation and that the functions are safe.
- Explicitly define a final object() to prevent deserialization.
More Deserialization of Untrusted Data vulnerabilities (CWE-502)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
References
Other references
Recent Deserialization of Untrusted Data vulnerabilities
- 9.8 Critical severity
- 8.1 High severity
- 9.8 Critical severity
- 8.0 High severity
- 9.3 Critical severity
- 7.5 High severity
Spotted an error? Tell us.