Security readout for executives and security teams
Plain-English summary
On affected vivo Android devices, a malicious app with some privileges could abuse incorrect PendingIntent handling in the Framework/Frame service to perform privileged actions. The main concern is data exposure, with high confidentiality impact in the CVSS vector. The issue is local and requires user interaction, so it is not described as a remote network worm risk.
Executive priority
Prioritize remediation if vivo devices are used for business data, executives, field staff, or BYOD access. The vulnerability is medium severity, but the confidentiality impact is high. If vivo devices are not present, record non-exposure and monitor vendor guidance.
Technical view
CVE-2021-26277 is a PendingIntent hijacking issue in vivo Frame service version 2021.6.30. The published CVSS 3.1 score is 5.6: local attack vector, low complexity, low privileges required, user interaction required, unchanged scope, high confidentiality impact, low integrity impact, and no availability impact.
Likely exposure
Likely exposure is limited to environments with vivo devices using the affected Frame service version 2021.6.30. The provided sources do not identify broader Android, non-vivo, or later-version exposure. Organizations without managed vivo mobile devices likely have low direct exposure, but BYOD fleets should still be checked.
Exploitation context
The source bundle does not show CISA KEV listing or public active exploitation evidence. Exploitation would require local app execution, some privileges, and user interaction. Treat this as a targeted mobile risk until vendor or threat-intelligence sources provide stronger evidence.
Researcher notes
The public description is sparse and does not provide model lists, fixed versions, or detailed root-cause evidence in the source bundle. Avoid assuming exploitability beyond PendingIntent hijacking in vivo Frame service 2021.6.30. Validate against vendor advisory data before making fleet-wide conclusions.
Mitigation direction
- Check vivo security advisory guidance for affected models and available updates.
- Update affected vivo devices to a vendor-supported fixed firmware or security release.
- Restrict installation of untrusted or sideloaded Android applications.
- Use MDM controls to inventory vivo devices and enforce update compliance.
- Review BYOD policy coverage for unmanaged vivo devices.
Validation and detection
- Inventory vivo devices and identify Frame service or firmware versions.
- Compare device versions against vivo advisory details for CVE-2021-26277.
- Confirm affected devices have received vendor-recommended security updates.
- Review MDM logs for sideloading, risky app sources, or unusual app permissions.
- Document any devices that cannot be updated and apply compensating controls.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2021-26277 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:N1.34.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.6MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.vivo.com/en/support/security-advisory-detail?id=8CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.