# CVE-2025-1479: Security feature bypass in Legion Space for Legion Go

> A local attacker can execute arbitrary code via an open debug interface in Lenovo Legion Space software.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 May 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-mj3f-8797-c7r5

## What is CVE-2025-1479?

CVE-2025-1479 is a medium-severity vulnerability in Lenovo Legion Space for Legion Go, published on 30 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An open debug interface was reported in the Legion Space software included on certain Legion devices that could allow a local attacker to execute arbitrary code.

Weakness: CWE-489 (Active Debug Code)

## Which versions are affected by CVE-2025-1479?


## How do I fix CVE-2025-1479?

No fix has been published for CVE-2025-1479 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-1479 being exploited?

There is no known exploitation of CVE-2025-1479 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-1479 and fix it if it is affected.

What it is: CVE-2025-1479 is a medium-severity vulnerability in Lenovo Legion Space for Legion Go, published on 30 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-1479 in the wild and no public exploit code.

Affected product: Lenovo Legion Space for Legion Go. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-1479/ (Markdown: https://insights.sbomify.com/CVE-2025-1479/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-1479
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-1479
- OSV: https://osv.dev/vulnerability/CVE-2025-1479

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-1479/
Summaries are generated and may contain mistakes; the official description above is the record.