Incorrect signature verification on Google play-services-basement in Google Play SDK
Priority MEDIUM 43CWE-501Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA.
Summary
Incorrect signature trust exists within Google Play services SDK play-services-basement. A debug version of Google Play services is trusted by the SDK for devices that are non-GMS. We recommend upgrading the SDK past the 2022-05-03 release.
Why it matters now
Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00309 23rd percentileScored 2026-11-07
Fix Fixed Google Play Services SDK (Google LLC): 18.0.2
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
- Fix · CNA Google Play Services SDK (Google LLC) Fixed in 18.0.2
Timeline
- 2026-10-02 Threatist record created from CVE-2022-1799
- 2026-10-03 Alias added: GHSA-qfhf-vjgv-mm2w
References
More Google Play Services Software Development Kit vulnerabilities
- TI-2022-02206 Mutable pending intent in Google Play services SDK CVSS 3.1HIGH 8.4
Sources
- CVE-2022-1799 · CVE Program
- CVE-2022-1799 · NVD
- FIRST EPSS
- GHSA-qfhf-vjgv-mm2w · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences