CVE-2021-26277 json
Security Advisory | PendingIntent hijacking vulnerability in Framework Services
published 3y ago modified 4mo ago also EUVD-2021-13089
- cvss
- 5.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 27%
- public exploits
- 0
- none known
Summary
The framework service handles pendingIntent incorrectly, allowing a malicious application with certain privileges to perform privileged actions.
Patch / fix
- vivo frame_service 2021.6.30
Is CVE-2021-26277 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.6 | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:N |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- vivo Frame service
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
References
-
vivo.com
/en/support/security-advisory-detail?id=8
vendor-advisory
Sources
- CVE List CVE-2021-26277
- NVD CVE-2021-26277
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.