What is GHSA-68C2-4MPX-QH95?

GHSA-68C2-4MPX-QH95 is a low-severity security vulnerability in @sentry/react-native (npm), affecting versions >= 5.16.0, <= 5.19.0. It is fixed in 5.19.1.

Which versions of @sentry/react-native are affected by GHSA-68C2-4MPX-QH95?

@sentry/react-native (npm) versions >= 5.16.0, <= 5.19.0 is affected.

Is there a fix for GHSA-68C2-4MPX-QH95?

Yes. GHSA-68C2-4MPX-QH95 is fixed in 5.19.1. Upgrade to this version or later.

Is GHSA-68C2-4MPX-QH95 exploitable, and should I be worried?

Whether GHSA-68C2-4MPX-QH95 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-68C2-4MPX-QH95 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix GHSA-68C2-4MPX-QH95?

Upgrade @sentry/react-native to 5.19.1 or later.

GHSA-68C2-4MPX-QH95 in @sentry/react-native

Q: Which versions of @sentry/react-native are affected by GHSA-68C2-4MPX-QH95?

@sentry/react-native (npm) versions >= 5.16.0, <= 5.19.0 is affected.

Q: Is there a fix for GHSA-68C2-4MPX-QH95?

Yes. GHSA-68C2-4MPX-QH95 is fixed in 5.19.1. Upgrade to this version or later.

Q: Is GHSA-68C2-4MPX-QH95 exploitable, and should I be worried?

Whether GHSA-68C2-4MPX-QH95 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-68C2-4MPX-QH95 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-68C2-4MPX-QH95?

Upgrade @sentry/react-native to 5.19.1 or later.

Summary

Potential leakage of Sentry auth tokens by React Native SDK with Expo plugin

Workarounds

Remove authToken from the plugin configuration.
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.

References

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.

Affected versions

@sentry/react-native (>= 5.16.0, <= 5.19.0)

Security releases

@sentry/react-native → 5.19.1 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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.

Frequently Asked Questions

What is GHSA-68C2-4MPX-QH95? GHSA-68C2-4MPX-QH95 is a low-severity security vulnerability in @sentry/react-native (npm), affecting versions >= 5.16.0, <= 5.19.0. It is fixed in 5.19.1.
Which versions of @sentry/react-native are affected by GHSA-68C2-4MPX-QH95? @sentry/react-native (npm) versions >= 5.16.0, <= 5.19.0 is affected.
Is there a fix for GHSA-68C2-4MPX-QH95? Yes. GHSA-68C2-4MPX-QH95 is fixed in 5.19.1. Upgrade to this version or later.
Is GHSA-68C2-4MPX-QH95 exploitable, and should I be worried? Whether GHSA-68C2-4MPX-QH95 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-68C2-4MPX-QH95 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-68C2-4MPX-QH95? Upgrade @sentry/react-native to 5.19.1 or later.