Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain shared network position
-
DeliveryIntercept WebView content traffic
-
ExploitInject malicious JavaScript payload
-
ExecutionAbuse Weex stream and granted permissions
-
ImpactExfiltrate files, camera, GPS, clipboard
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Dangerous method exposure prevention
|
| Exploitation Conditions | The attacker must hold an adjacent network position (AV:A) shared with the victim and be able to intercept/tamper with content loaded into the app's WebView - implying interceptable or cleartext content delivery - in order to inject JavaScript; this is the core prerequisite (reflected by AT:P). No authentication is required (PR:N) and no user interaction is needed (UI:N). Baseline impact in the default state is limited to clipboard, app-internal storage, and arbitrary HTTP requests via the Weex 'stream' module. The escalated impact - entire filesystem, camera, microphone, and GPS - is CONDITIONAL on the installed app having previously been granted those OS-level permissions; on an install without those grants, exploitation is confined to the lower-impact set. The principal limiting factor is the adjacency/network-interception requirement, which prevents remote internet-based exploitation. |
| Impact | The CVSS 4.0 base score of 9.0 (Critical) reflects AV:A/AC:L/AT:P/PR:N/UI:N with full High impact to both vulnerable and subsequent systems (VC/VI/VA:H, SC/SI/SA:H), consistent with a WebView JavaScript-injection flaw (CWE-749, exposed dangerous method) that can escalate to filesystem, camera, microphone, and GPS access. However, several real-risk-dampening signals exist: the Adjacent attack vector (AV:A) means the attacker must share the victim's local network rather than attack over the internet, and AT:P signals a specific attack requirement (network interception position), so this is not internet-wide drive-by exploitation. No EPSS score, no CISA KEV listing, and no public POC are present in the provided data, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The highest-impact outcomes (entire filesystem, camera, mic, GPS) are conditional on the app having been previously granted those OS permissions - a conflict worth highlighting: the headline 9.0 assumes the maximal permission-granted state, whereas the default no-prior-permission state is limited to clipboard, app-internal storage, and arbitrary HTTP via the Weex 'stream' module. Net: a genuinely serious client-side flaw for users on hostile Wi-Fi, but the adjacency requirement and consumer-app footprint make it a targeted/opportunistic local-network risk rather than a mass-exploitation emergency. |
| Exploit ScenarioDerived | A victim uses the Joyland AI app while connected to an attacker-controlled or shared network (e.g., public Wi-Fi). The attacker intercepts and tampers with content loaded into the app's WebView, injecting JavaScript that abuses the Weex 'stream' module and exposed interfaces to read the clipboard and app-internal storage, and - if the app was previously granted device permissions - to access the filesystem, camera, microphone, and GPS. No public exploit code is identified in the provided data, and no user interaction (UI:N) is required once the attacker holds the network position. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 01, 2026
JavaScript injection into the WebView of the Joyland AI app (all versions, tracked as CPE cpe:2.3:a:joyland:joyland.ai:*) lets an attacker who shares a network position with the victim and can intercept or tamper with content loaded into the app run arbitrary script inside the app's privileged context; no authentication is required and no user interaction is needed. In the default, unpermissioned install state the attacker can read the device clipboard, make arbitrary HTTP requests through the Weex 'stream' module, and reach app-internal storage, while on devices that previously granted camera, microphone, location, or storage permissions the same flaw escalates to full filesystem, camera, microphone, and GPS access. No public exploit code and no confirmed active exploitation were identified at time of analysis, and no vendor-released patch has been identified; the CVSS 4.0 base score is 9.0 (Critical) and EPSS data was not provided for this record.
RemediationAI
No vendor-released patch has been identified at time of analysis, so remediation is currently compensatory. The most effective control is to remove the prerequisite for exploitation by ensuring all content loaded into the app's WebView is delivered over authenticated TLS and is not interceptable on the local network - enforcing certificate pinning in the app and refusing to load over cleartext HTTP or from unauthenticated proxies breaks the adjacent-network tampering path required by the AV:A/AT:P vector; the trade-off is that any pinned or hard-ended hostname the app still calls in cleartext will fail to load. Where the bridge itself can be constrained, disabling JavaScript in the WebView, or restricting the Weex 'stream' module and other addJavascriptInterface-exposed methods so they are not reachable from remotely loaded content, removes the injection-to-native capability at the cost of breaking features that depend on those bridges. Because escalation to filesystem, camera, microphone, and GPS is conditional on pre-existing OS permission grants, revoking camera, microphone, and location permissions from the Joyland AI app in device settings - and confirming the app is not granted broad storage access - caps the blast radius to clipboard, HTTP request, and app-internal storage impact; note that this degrades or disables legitimate in-app camera, voice, and location features. Users should also avoid untrusted or shared Wi-Fi networks while using the app, or route app traffic through a trusted VPN, and enterprise administrators should treat the app as untrusted on managed devices until the vendor ships a fixed build. Monitor the vendor and the CVE.org record (https://www.cve.org/CVERecord?id=CVE-2026-1026667) as well as the CISA CSAF feed (https://raw.githubusercontent.com/cisagov/CSAF/develop/csaf_files/IT/white/2026/va-26-275-03.json) for a patched release, since the current references contain no fix version.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause class is CWE-749 (Exposed Dangerous Method or Function): the Joyland AI app embeds a WebView whose JavaScript bridge and the Weex 'stream' module expose powerful native capabilities to content the app loads, without sufficiently validating or isolating that content. Because the flaw lives in the interaction between the WebView and the native bridge rather than in a server-side component, exploitation hinges on the attacker being able to intercept or modify the material that the app pulls into the WebView - consistent with the assessed AV:A (adjacent network) vector and the AT:P (attack requirements present) value in both the CVSS 4.0 vector (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) and the independent CVSS 3.1 assessment (AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H). Neither vector includes a PR:L or PR:H value, so the attack is unauthenticated; both include UI:N, so no victim interaction is required. Injected JavaScript executes with the app's own privileges rather than a browser sandbox, which is why the exposed 'stream' bridge can be abused for arbitrary HTTP requests and why app-internal storage is reachable by default. Impact is scope-changing (S:C in the 3.1 vector, with SC/SI/SA:H in the 4.0 vector) because the fl aw crosses from the web-content context into the native app and, where the app already holds OS permission grants, into the operating system itself.
Know when Joyland Ai gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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
AV:A and AC:H capture the required shared-network interception position; PR:N/UI:N per unauthenticated no-interaction injection; S:C and C/I/A:H reflect WebView escape to device resources.
Primary rating from Vendor (cisa-cg).
CVSS VectorVendor: cisa-cg
DescriptionCVE.org
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.
Executive ViewAI
Joyland AI's mobile app is affected in all released versions by a critical JavaScript injection flaw that lets anyone sharing a network path with a user execute code inside the app's privileged context, without any action by the victim. Because no vendor patch has been identified, devices where users have granted camera, microphone, location, or storage permissions could expose files, sensors, and GPS data to an attacker, and even default installs permit clipboard theft, app-internal storage access, and arbitrary outbound web requests. Leadership should treat this as an unpatched risk to any mobile estate where the app is installed, particularly on BYOD devices carrying corporate data.
No vendor-released patch identified at time of analysis. Interim mitigations: revoke the app's camera, microphone, location, and storage permissions; block or remove Joyland AI via MDM/UEM on devices holding corporate data; isolate it in a work profile with no access to corporate credentials or storage; require VPN or trusted-network-only connectivity and avoid untrusted networks while the app is in use; disable or restrict cross-app clipboard sharing; monitor mobile egress for unexpected HTTP traffic; and advise users to treat the app as untrusted until a vendor fix is available.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
More in Joyland Ai
View allThe Joyland.ai application fails to validate the hostname in TLS certificates presented by the server, allowing an attac
Hard-coded GeTui push-service credentials embedded in the Joyland AI client app let anyone who extracts them from a copy
Improper TLS certificate validation in the Joyland AI app causes its invisible advertisement WebView to accept invalid o
Man-in-the-middle interception of traffic between the Joyland AI application and its backend is possible because the app
Cleartext transmission of application traffic in the Joyland AI Android app exposes data to on-path attackers positioned
EUVD-2026-91025
GHSA-9jq9-g952-299j
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB