CVE-2026-49931
In onActivityResult in multiple locations, there is a possible contact leak from protected...
In onActivityResult in multiple locations, there is a possible contact leak from protected profile due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Attack profile
How easy it is to exploit
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Exploit likelihood
What each source reports
CVE List Score used
In onActivityResult in multiple locations, there is a possible contact leak from protected profile due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
- Record
CVE-2026-49931- CVSS 3.1
- 8.4 High
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Weakness
- CWE-441
- Updated
- 2026-11-03
EUVDEUVD-2026-115563
In onActivityResult in multiple locations, there is a possible contact leak from protected profile due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
- Record
EUVD-2026-115563- CVSS 3.1
- 8.4 High
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-03
GitHub AdvisoriesGHSA-m939-gjcq-3263
In onActivityResult in multiple locations, there is a possible contact leak from protected...
In onActivityResult in multiple locations, there is a possible contact leak from protected profile due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
- Record
GHSA-m939-gjcq-3263- CVSS 3.1
- 8.4 High
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Weakness
- CWE-441
- Updated
- 2026-11-03
NVD
In onActivityResult in multiple locations, there is a possible contact leak from protected profile due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
- Record
CVE-2026-49931- CVSS 3.1
- 8.4 High
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Weakness
- CWE-441
- Updated
- 2026-11-06
OSVASB-A-490916793 No score
In onActivityResult in multiple locations, there is a possible contact leak from protected profile due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
- Record
ASB-A-490916793- Updated
- 2026-11-06
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
platform/packages/services/TelephonyAndroid |
17-qpr2-next:0 up to 17-qpr2-next:2026-11-01, plus listed versions 17-qpr2-next |
17-qpr2-next:2026-11-01 |
platform/packages/services/TelephonyAndroid |
15:0 up to 15:2026-11-01, plus listed versions 15 |
15:2026-11-01 |
platform/packages/services/TelephonyAndroid |
16:0 up to 16:2026-11-01, plus listed versions 16 |
16:2026-11-01 |
platform/packages/services/TelephonyAndroid |
16-qpr2:0 up to 16-qpr2:2026-11-01, plus listed versions 16-qpr2 |
16-qpr2:2026-11-01 |
platform/packages/services/TelephonyAndroid |
17:0 up to 17:2026-11-01, plus listed versions 17 |
17:2026-11-01 |
platform/packages/services/TelephonyAndroid |
14:0 up to 14:2026-11-01, plus listed versions 14 |
14:2026-11-01 |
History
| Recorded | Changed | Sources |
|---|---|---|
| references | NVD | |
| references | NVD, OSV | |
| facts | CVE List, EUVD, NVD | |
| aliases | EUVD | |
| aliases, cwes, references, severity, title | CVE List, GitHub Advisories, NVD | |
| first indexed | CVE List, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2026-49931 is a high vulnerability (CVSS 8.4) in Google Android, published November 1, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.10%, the 0th percentile. Fixed in platform/packages/services/Telephony 17-qpr2-next:2026-11-01.