Quick answers
- Is CVE-2026-89229 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-89229 being exploited in the wild.
- How severe is CVE-2026-89229?
- Informational severity, published 3 November 2026.
- Which products and versions are affected?
- Vivo BlueLM Copilot below 7.2.0.0.
- Is there a fix for CVE-2026-89229?
- Yes: fixed in BlueLM Copilot 7.2.0.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-89229 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2026-89229?
- Check whether you run Vivo BlueLM Copilot at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: BlueLM Copilot 7.2.0.0
Technical details
The ShareActivity component in BlueLM Copilot fails to properly validate file paths in ACTION_SEND intents, allowing an attacker to use ".." sequences in ContentProvider-supplied file names to traverse directories and write files outside the intended location. Attack requires a malicious application to be installed locally on the device; no network or user interaction is needed. An attacker gains the ability to write arbitrary files, potentially compromising system integrity or installing malware.
Affected products
- vivo BlueLM Copilot below 7.2.0.0
Timeline
- 2026-11-03: disclosed