Skip to main content
CVE-2025-26461VulnerabilityPublished

CVE-2025-26461: Google Android · Information disclosure

Affects Google AndroidSource CVE Database V5

0

Not known to be exploited · CVSS 3.3 Low.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
3.3Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.08% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
Google AndroidAffected
  • =16
Fixed in–

AI-suggested

To mitigate this vulnerability, European organizations should prioritize updating affected Android devices to patched versions as soon as Google releases a fix. Until a patch is available, organizations should implement strict device usage policies, including restricting installation of untrusted applications and enforcing strong endpoint security controls. Employing mobile device management (MDM) solutions can help monitor and control microphone access and detect anomalous behavior related to permission indicators. Regular audits of device permissions and usage logs can identify potential exploitation attempts. Additionally, educating users about the importance of closing applications properly and reporting unusual device behavior can reduce risk. For high-security environments, consider using hardware-based microphone kill switches or disabling microphone access when not needed. Collaboration with device vendors and security teams to monitor for emerging exploits is also recommended.

Description

In Permission Manager, there is a possible way for the microphone privacy indicator to remain activated even after the user attempts to close the app due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

References

Community reviews

Loading reviews…