In queryRemoteConnectionServices of ConnectionServiceWrapper.java, there is a possible permission bypass due to a confused deputy.
Google Android is affected, and the advisory lists fixes for Android 14, 15, 16, and 16-qpr2. CVSS scores it 8.4 (high), and no vendor severity rating is given.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 14, 15, 16, 16-qpr2
- Who is exposed
- Specific setups only
Do first: Upgrade to a fixed version: 14, 15, 16, 16-qpr2.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 14/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 14, 15, 16, 16-qpr2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
The vulnerability affects the Android telephony framework's connection service component, which manages calling connections. A local attacker could exploit it to bypass permission checks and gain elevated privileges on the device, without needing extra execution rights or user interaction.
Read the original description
In queryRemoteConnectionServices of ConnectionServiceWrapper.java, there is a possible permission bypass 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.
What to do
Upgrade to a fixed version: 14, 15, 16, 16-qpr2.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Google Android
16-qpr2, 16, 15, 14
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-49922
What should I do about it?
Install a security update that includes the fix for your Android branch, which the advisory lists as 14, 15, 16, or 16-qpr2. The facts give no workaround, so updating is the only listed remedy.Source: source.android.com
Is it 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