# CVE-2026-6282: Path traversal in Home Storage Hub T20

> Remote authenticated users can move or access other users' files on Lenovo Personal Cloud Storage devices due to improper path validation.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 May 2026
- **Updated:** 13 May 2026
- **Also known as:** GHSA-m6vj-6h49-wg69

## What is CVE-2026-6282?

CVE-2026-6282 is a high-severity path traversal vulnerability in Lenovo Home Storage Hub T20, published on 13 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A potential improper file path validation vulnerability was reported in some Lenovo Personal Cloud Storage devices that could allow a remote authenticated user to move or access files belonging to other users on the same device.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-6282?


## How do I fix CVE-2026-6282?

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

## Is CVE-2026-6282 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6282 and fix it if it is affected.

What it is: CVE-2026-6282 is a high-severity path traversal vulnerability in Lenovo Home Storage Hub T20, published on 13 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-6282 in the wild and no public exploit code.

Affected product: Lenovo Home Storage Hub T20. 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-2026-6282/ (Markdown: https://insights.sbomify.com/CVE-2026-6282/index.md)
```

## Sources

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

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