Google Play Services SDK leads to apps having incorrectly set mutability flag

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.1 · CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:L/A:N

EPSS

• CVE-2022-2390: 0.11% estimated exploitation activity in the next 30 days; percentile 1.26 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Apps developed with Google Play Services SDK incorrectly had the mutability flag set to PendingIntents that were passed to the Notification service. As Google Play services SDK is so widely used, this bug affects many applications. For an application affected, this bug will let the attacker, gain the access to all non-exported providers and/or gain the access to other providers the victim has permissions. We recommend upgrading to version 18.0.2 of the Play Service SDK as well as rebuilding and redeploying apps.

Published by the source

13 Aug 2022, 00:00 UTC

Last modified by the source

30 Jan 2023, 05:06 UTC

Source last checked

26 Oct 2026, 16:02 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-cm6r-892j-jv2g

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-2390

Advisory: Google Play Services SDK leads to apps having incorrectly set mutability flag
IDs: CVE-2022-2390, GHSA-cm6r-892j-jv2g
Record: https://patchnext.com/advisories/cve-2022-2390 (revision 1, source checked 26 Oct 2026, 16:02 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.google.android.gms:play-services-basement 18.0.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.google.android.gms:play-services-basement: affected < 18.0.2; fixed in 18.0.2

## Suggested inspection (read-only)
- Maven com.google.android.gms:play-services-basement: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.google.android.gms:play-services-basement.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-cm6r-892j-jv2g (GitHub-reviewed advisory GHSA-cm6r-892j-jv2g lists affected ranges: Maven com.google.android.gms:play-services-basement >=0 <18.0.2)

Commands are suggestions: review each one before running it.