Summary
Potential DoS when using ContextLines integration
Workarounds
To remediate this issue in affected versions without upgrading to version 8.49.0 and above you can disable the ContextLines integration. See the docs for more details.
Sentry.init({
// ...
integrations: function (integrations) {
// integrations will be all default integrations
return integrations.filter(function (integration) {
return integration.name !== "ContextLines";
});
},
});
If you disable the ContextLines integration, you will lose source context on your error events.
References
Impact
The ContextLines integration uses readable streams to more efficiently use memory when reading files. The ContextLines integration is used to attach source context to outgoing events.
The stream was not explicitly closed after use. This could lead to excessive amounts of file handles open on the system and potentially lead to a Denial of Service (DoS).
The ContextLines integration is enabled by default in the Node SDK (@sentry/node) and SDKs that run in Node.js environments (@sentry/astro, @sentry/aws-serverless, @sentry/bun, @sentry/google-cloud-serverless, @sentry/nestjs, @sentry/nextjs, @sentry/nuxt, @sentry/remix, @sentry/solidstart, @sentry/sveltekit).
GHSA-R5W7-F542-Q2J4 has a CVSS score of 3.7 (Low). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (8.49.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
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 environmentNew to Kodem? Get a demo →Remediation advice
Users should upgrade to version 8.49.0 or higher.
Frequently Asked Questions
- What is GHSA-R5W7-F542-Q2J4? GHSA-R5W7-F542-Q2J4 is a low-severity security vulnerability in @sentry/node (npm), affecting versions >= 8.10.0, < 8.49.0. It is fixed in 8.49.0.
- How severe is GHSA-R5W7-F542-Q2J4? GHSA-R5W7-F542-Q2J4 has a CVSS score of 3.7 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which packages are affected by GHSA-R5W7-F542-Q2J4?
@sentry/node(npm) (versions >= 8.10.0, < 8.49.0)@sentry/astro(npm) (versions >= 8.10.0, < 8.49.0)@sentry/aws-serverless(npm) (versions >= 8.10.0, < 8.49.0)@sentry/bun(npm) (versions >= 8.10.0, < 8.49.0)@sentry/google-cloud-serverless(npm) (versions >= 8.10.0, < 8.49.0)@sentry/nestjs(npm) (versions >= 8.10.0, < 8.49.0)@sentry/nextjs(npm) (versions >= 8.10.0, < 8.49.0)@sentry/nuxt(npm) (versions >= 8.10.0, < 8.49.0)@sentry/remix(npm) (versions >= 8.10.0, < 8.49.0)@sentry/solidstart(npm) (versions >= 8.10.0, < 8.49.0)@sentry/sveltekit(npm) (versions >= 8.10.0, < 8.49.0)
- Is there a fix for GHSA-R5W7-F542-Q2J4? Yes. GHSA-R5W7-F542-Q2J4 is fixed in 8.49.0. Upgrade to this version or later.
- Is GHSA-R5W7-F542-Q2J4 exploitable, and should I be worried? Whether GHSA-R5W7-F542-Q2J4 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-R5W7-F542-Q2J4 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-R5W7-F542-Q2J4?
- Upgrade
@sentry/nodeto 8.49.0 or later - Upgrade
@sentry/astroto 8.49.0 or later - Upgrade
@sentry/aws-serverlessto 8.49.0 or later - Upgrade
@sentry/bunto 8.49.0 or later - Upgrade
@sentry/google-cloud-serverlessto 8.49.0 or later - Upgrade
@sentry/nestjsto 8.49.0 or later - Upgrade
@sentry/nextjsto 8.49.0 or later - Upgrade
@sentry/nuxtto 8.49.0 or later - Upgrade
@sentry/remixto 8.49.0 or later - Upgrade
@sentry/solidstartto 8.49.0 or later - Upgrade
@sentry/sveltekitto 8.49.0 or later
- Upgrade