CVE-2025-22425: Google Android · Elevation of Privilege
Affects Google AndroidSource CVE Database V5
Not known to be exploited · CVSS 5.1 Medium.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.09% 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:N/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 4 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Google Android | Affected
| Fixed in– |
AI-suggested
Organizations and users should monitor for official patches from Google and apply them promptly once available. Until patches are released, enforcing strict app installation policies—such as restricting installations to trusted sources like the Google Play Store—and educating users about the risks of installing unknown applications can reduce exposure. Employing mobile device management (MDM) solutions to control app permissions and monitor device behavior can help detect and prevent exploitation attempts. Additionally, security teams should audit device configurations to ensure minimal privileges are granted to apps and services, and consider deploying runtime protection tools that can detect anomalous privilege escalation behaviors. Regular security awareness training emphasizing cautious user interaction with apps and links is also recommended to mitigate the user interaction requirement for exploitation.
Description
In onCreate of InstallStart.java, there is a possible permissions bypass due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.