Vivo Assistant unauthorized voice commands in ChatEventDispatchActivity
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Not reported
Summary
An improper export control defect in ChatEventDispatchActivity of Vivo Assistant (package com.vivo.agent) lets a malicious app installed on the same device run voice commands without any user interaction by sending a crafted Intent. An attacker could use this to make unauthorized phone calls, send SMS messages, access private data such as location and calendar entries, or change system settings.
Written by a model
Original description
An improper export control defect in ChatEventDispatchActivity (com.vivo.agent.business.chatmode.activity.ChatEventDispatchActivity) of Vivo Assistant allows a local malicious application to execute voice commands without user interaction via a crafted Intent, which may lead to unauthorized phone calls, SMS sending, access to private data such as location and calendar entries, and modification of system settings
What to do
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-15223 (An improper export control defect in ChatEventDispatchActivity (com.vivo.agent.business.chatmode.activity.ChatEventDispatchActivity) of…), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-15223 (entry last updated 2026-11-20):
Affected:
- vivo Vivo Assistant: versions Versions below 27.0.0.1
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-15223 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-15223 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.vivo.com/en/support/security-advisory-detail?id=27
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-15223
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-15223"}.Affected versions
- com.vivo.agentVersions below 27.0.0.1
cve.now Index
- Exploitation0/40No signal
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.1/10CVSS 5.1
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Link | vivo.com · en/support/security-advisory-detail?id=27 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-15223 |
| Record | NVD · CVE-2026-15223 |
Questions about CVE-2026-15223
Is CVE-2026-15223 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-15223?
com.vivo.agent: version Versions below 27.0.0.1.
Source: cve.now feed data
Related
- CVE-2026-11535An unauthorized access vulnerability exists in the PcSuite APP.
- CVE-2021-26280Permission bypass vulnerability in permission manager module
- CVE-2025-15509The SmartRemote module has insufficient restrictions on loading URLs, which may lead to some information leakage.
- CVE-2020-12487Command Execution Vulnerability in ABE service
- CVE-2025-15515The authentication mechanism for a specific feature in the EasyShare module contains a vulnerability.
- CVE-2020-12484When using special mode to connect to enterprise wifi, certain options are not properly configured and attackers can pretend to be enterpris
No corrections so far. Something wrong on this page? Report an error.