GHSA-r5w7-f542-q2j4 is a low-severity (CVSS 3.7) vulnerability in @sentry/node. A fix is available for @sentry/node — see the affected versions and patch details below.
Potential DoS when using ContextLines integration
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@sentry/nodenpm@sentry/astronpm@sentry/aws-serverlessnpmDescription
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).
Patches
Users should upgrade to version 8.49.0 or higher.
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @sentry/node | ≥ 8.10.0&&< 8.49.0 | 8.49.0npm install @sentry/node@8.49.0 |
| 📦npm | @sentry/astro | ≥ 8.10.0&&< 8.49.0 | 8.49.0npm install @sentry/astro@8.49.0 |
| 📦npm | @sentry/aws-serverless | ≥ 8.10.0&&< 8.49.0 | 8.49.0npm install @sentry/aws-serverless@8.49.0 |
| 📦npm | @sentry/bun | ≥ 8.10.0&&< 8.49.0 | 8.49.0npm install @sentry/bun@8.49.0 |
| 📦npm | @sentry/google-cloud-serverless | ≥ 8.10.0&&< 8.49.0 | 8.49.0npm install @sentry/google-cloud-serverless@8.49.0 |
| 📦npm | @sentry/nestjs | ≥ 8.10.0&&< 8.49.0 | 8.49.0npm install @sentry/nestjs@8.49.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @sentry/node, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @sentry/node to 8.49.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r5w7-f542-q2j4 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-r5w7-f542-q2j4 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-r5w7-f542-q2j4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-r5w7-f542-q2j4 in your dependencies?
O3 Security finds GHSA-r5w7-f542-q2j4 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.