# CVE-2026-22070: ColorOS Assistant Path Traversal Vulnerability

> An unauthenticated path traversal in ColorOS Assistant allows attackers to read or modify arbitrary files on the device.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Apr 2026
- **Updated:** 30 Apr 2026
- **Also known as:** GHSA-p7qv-vx32-p4gg

## What is CVE-2026-22070?

CVE-2026-22070 is a high-severity path traversal vulnerability in OPPO ColorOS Assistant, published on 30 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

ColorOS Assistant has an unauthenticated start-download channel, leading to file path traversal.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-23 (Relative Path Traversal)

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

It affects 1 product.


Products: Oppo Coloros Assistant.

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

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

## Is CVE-2026-22070 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-22070 is a high-severity path traversal vulnerability in OPPO ColorOS Assistant, published on 30 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-22070 in the wild and no public exploit code.

Affected product: OPPO ColorOS Assistant. 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-22070/ (Markdown: https://insights.sbomify.com/CVE-2026-22070/index.md)
```

## Sources

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

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