cve.bz

CVE-2026-56947 google android: Confused Deputy

4.0 mediumEPSS 0.1%

Medium (4.0) in google android. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
In getCarrierRestrictionStatus of PhoneInterfaceManager.java, there is a possible permission bypass due to a confused deputy. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

Severity

CVSS 3.1

4.0 medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
0.1% estimated probability of exploitation activity in the next 30 days; 2nd percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-441 Unintended Proxy or Intermediary (Confused Deputy)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
Assigned by
Google_Devices (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-56947 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-56947?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-56947?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-56947 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-56947

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-56947](https://cve.bz/cve/badge/CVE-2026-56947.svg)](https://cve.bz/cve/CVE-2026-56947)

HTML:

<a href="https://cve.bz/cve/CVE-2026-56947"><img src="https://cve.bz/cve/badge/CVE-2026-56947.svg" alt="CVE-2026-56947"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Google AndroidAndroid kernel

Attack patterns (CAPEC)

  • CAPEC-219 XML Routing Detour Attacks Likelihood: High · Severity: Medium
  • CAPEC-465 Transparent Proxy Abuse Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

History

  1. Scored 4.0 medium

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON