GHSA-68c2-4mpx-qh95
Potential leakage of Sentry auth tokens by React Native SDK with Expo plugin
Impact
SDK versions between and including 5.16.0 and 5.19.0 allowed Sentry auth tokens to be set in the optional authToken configuration parameter, for debugging purposes. Doing so would result in the auth token being built into the application bundle, and therefore the auth token could be potentially exposed in case the application bundle is subsequently published.
You may ignore this notification if you are not using authToken configuration parameter in your React Native SDK configuration or did not publish apps using this way of configuring the authToken.
If you had set the authToken in the plugin config previously, and built and published an app with that config, you should rotate your token.
Patches
The behavior that allowed setting an authToken parameter was fixed in SDK version 5.19.1 where, if this parameter was set, you will see a warning and the authToken would be removed before bundling the application.
Workarounds
- Remove
authTokenfrom the plugin configuration. - If you had set the
authTokenin the plugin config previously, and built and published an app with that config, you should rotate your token.
References
What each source reports
GitHub AdvisoriesNo score
Potential leakage of Sentry auth tokens by React Native SDK with Expo plugin
Impact
SDK versions between and including 5.16.0 and 5.19.0 allowed Sentry auth tokens to be set in the optional authToken configuration parameter, for debugging purposes. Doing so would result in the auth token being built into the application bundle, and therefore the auth token could be potentially exposed in case the application bundle is subsequently published.
You may ignore this notification if you are not using authToken configuration parameter in your React Native SDK configuration or did not publish apps using this way of configuring the authToken.
If you had set the authToken in the plugin config previously, and built and published an app with that config, you should rotate your token.
Patches
The behavior that allowed setting an authToken parameter was fixed in SDK version 5.19.1 where, if this parameter was set, you will see a warning and the authToken would be removed before bundling the application.
Workarounds
- Remove
authTokenfrom the plugin configuration. - If you had set the
authTokenin the plugin config previously, and built and published an app with that config, you should rotate your token.
References
- Record
GHSA-68c2-4mpx-qh95- Weakness
- CWE-200
- Updated
- 2026-11-02
OSVNo score
Potential leakage of Sentry auth tokens by React Native SDK with Expo plugin
Impact
SDK versions between and including 5.16.0 and 5.19.0 allowed Sentry auth tokens to be set in the optional authToken configuration parameter, for debugging purposes. Doing so would result in the auth token being built into the application bundle, and therefore the auth token could be potentially exposed in case the application bundle is subsequently published.
You may ignore this notification if you are not using authToken configuration parameter in your React Native SDK configuration or did not publish apps using this way of configuring the authToken.
If you had set the authToken in the plugin config previously, and built and published an app with that config, you should rotate your token.
Patches
The behavior that allowed setting an authToken parameter was fixed in SDK version 5.19.1 where, if this parameter was set, you will see a warning and the authToken would be removed before bundling the application.
Workarounds
- Remove
authTokenfrom the plugin configuration. - If you had set the
authTokenin the plugin config previously, and built and published an app with that config, you should rotate your token.
References
- Record
GHSA-68c2-4mpx-qh95- Weakness
- CWE-200
- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
@sentry/react-nativenpm | 5.16.0 to 5.19.0 | 5.19.1 |
@sentry/react-nativenpm | 5.16.0 up to 5.19.1 | 5.19.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
GHSA-68c2-4mpx-qh95 is a vulnerability with no CVSS score yet in @sentry/react-native, published March 1, 2024. No source lists public exploit code. Fixed in @sentry/react-native 5.19.1.
References
github.com/getsentry/sentry-react-native/security/advisories/GHSA-68c2-4mpx-qh95