# CVE-2026-102667: Joyland AI WebView command injection

> Attackers on the same network can inject JavaScript into the Joyland AI WebView, potentially accessing sensitive data and device features.

- **Severity:** Critical 9.0 (`CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-9jq9-g952-299j

## What is CVE-2026-102667?

CVE-2026-102667 is a critical code injection vulnerability in Joyland.ai, published on 1 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Joyland AI app allows an attacker with shared network access to inject JavaScript into content loaded in WebView. Without user-granted permissions, an attacker could access the clipboard, make arbitrary HTTP requests via the Weex 'stream' module, or access app-internal storage.  If the installed app has been granted permissions previously, the attacker can access the entire file system, camera, microphone, and GPS tracking.

Weakness: CWE-749 (Exposed Dangerous Method or Function)

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


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

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

## Is CVE-2026-102667 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-102667 is a critical code injection vulnerability in Joyland.ai, published on 1 Oct 2026. 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-2026-102667 in the wild and no public exploit code.

Affected product: Joyland.ai. 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-102667/ (Markdown: https://insights.sbomify.com/CVE-2026-102667/index.md)
```

## Sources

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

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