# CVE-2026-102671: Joyland AI WebView accepts invalid SSL certificates

> The Joyland AI mobile app accepts invalid SSL certificates in its advertisement WebView, allowing attackers to intercept or modify traffic.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Oct 2026
- **Updated:** 11 Oct 2026
- **Also known as:** GHSA-vgxg-97fh-vqcv

## What is CVE-2026-102671?

CVE-2026-102671 is a medium-severity vulnerability in Joyland.ai, published on 1 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Joyland AI app accepts invalid SSL certificates in the invisible advertisement WebView by default.

Weakness: CWE-295 (Improper Certificate Validation)

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


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

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

## Is CVE-2026-102671 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-102671 is a medium-severity vulnerability in Joyland.ai, published on 1 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-102671 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-102671/ (Markdown: https://insights.sbomify.com/CVE-2026-102671/index.md)
```

## Sources

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

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