sentry-android unmasked sensitive data in Android Session Replays for users of Jetpack Compose 1.8+

Exploitation

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

CVSS 4.0

8.2 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Impact Under specific circumstances, text composables may contain unmasked sensitive data in Android session replays. You may be impacted if you meet the following conditions: - Using any sentry-android with versions < 8.14.0 - Using Jetpack Compose = 1.8.0-alpha08 - This includes any alpha, beta, release candidate, or general availability after this version - Have configured Sentry Session Replays for Android [!IMPORTANT] If you do not use Jetpack Compose or have never used a version = 1.8.0-alpha08 you are not impacted. [!IMPORTANT] If you have not configured Session Replays for Mobile you are not impacted. How do I check if I'm impacted? If you meet the conditions above, the sentry-android package includes a specific error log that would indicate you may be impacted. Customers may use logcat to search for this event. I'm impacted and want this data deleted If you've confirmed that you're affected and unmasked sensitive data in Session Replays have reached Sentry servers, you can…

Published by the source

20 Jun 2025, 13:28 UTC

Last modified by the source

20 Jun 2025, 19:27 UTC

Source last checked

26 Oct 2026, 16:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-7cjh-xx4r-qh3f

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

# Patch Next advisory brief: GHSA-7cjh-xx4r-qh3f

Advisory: sentry-android unmasked sensitive data in Android Session Replays for users of Jetpack Compose 1.8+
IDs: GHSA-7cjh-xx4r-qh3f
Record: https://patchnext.com/advisories/ghsa-7cjh-xx4r-qh3f (revision 1, source checked 26 Oct 2026, 16:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: io.sentry:sentry-android 8.14.0; io.sentry:sentry-android-replay 8.14.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven io.sentry:sentry-android: affected < 8.14.0; fixed in 8.14.0
- Maven io.sentry:sentry-android-replay: affected < 8.14.0; fixed in 8.14.0

## Suggested inspection (read-only)
- Maven io.sentry:sentry-android: check the installed version with your package manager.
- Maven io.sentry:sentry-android-replay: 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 io.sentry:sentry-android, io.sentry:sentry-android-replay.
- 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-7cjh-xx4r-qh3f (GitHub-reviewed advisory GHSA-7cjh-xx4r-qh3f lists affected ranges: Maven io.sentry:sentry-android >=0 =0 <8.14.0)

Commands are suggestions: review each one before running it.