GHSA-6465-jgvq-jhgp
GHSA-6465-jgvq-jhgp is a CWE-201 vulnerability in @sentry/node. O3 Security confirms whether GHSA-6465-jgvq-jhgp is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Sentry's sensitive headers are leaked when `sendDefaultPii` is set to `true`
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
@sentry/nodenpm@sentry/astronpm@sentry/aws-serverlessnpmDescription
Impact
In version 10.11.0, a change to how the SDK collects request data in Node.js applications caused certain incoming HTTP headers to be added as trace span attributes. When sendDefaultPii: true was set, a few headers that were previously redacted - including Authorization and Cookie - were unintentionally allowed through.
Sentry’s server-side scrubbing (handled by Sentry's Relay edge proxy) normally serves as a second layer of protection. However, because it relied on the same matching logic as the SDK, it also failed to catch these headers in this case.
Users may be impacted if:
- Their Sentry SDK configuration has
sendDefaultPiiset totrue - Their application uses one of the Node.js Sentry SDKs with version from
10.11.0to10.26.0inclusively:
- @sentry/astro
- @sentry/aws-serverless
- @sentry/bun
- @sentry/google-cloud-serverless
- @sentry/nestjs
- @sentry/nextjs
- @sentry/node
- @sentry/node-core
- @sentry/nuxt
- @sentry/remix
- @sentry/solidstart
- @sentry/sveltekit
Users can check if their project was affected, by visiting Explore → Traces and searching for “http.request.header.authorization”, “http.request.header.cookie” or similar. Any potentially sensitive values will be specific to users' applications and configurations.
Patches
The issue has been patched in all Sentry JavaScript SDKs starting from the 10.27.0 version.
Workarounds
Sentry strongly encourage customers to upgrade the SDK to the latest available version, 10.27.0 or later.
If it is not possible, consider setting sendDefaultPii: false to avoid unintentionally sending sensitive headers. See here for documentation.
Resources
- https://develop.sentry.dev/sdk/expected-features/data-handling/#sensitive-data
- https://github.com/getsentry/sentry-javascript/releases/tag/10.11.0
- https://github.com/getsentry/sentry-javascript/pull/17475
- https://docs.sentry.io/platforms/javascript/guides/node/data-management/data-collected/#cookies
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @sentry/node | ≥ 10.11.0&&< 10.27.0 | 10.27.0 |
| 📦npm | @sentry/astro | ≥ 10.11.0&&< 10.27.0 | 10.27.0 |
| 📦npm | @sentry/aws-serverless | ≥ 10.11.0&&< 10.27.0 | 10.27.0 |
| 📦npm | @sentry/bun | ≥ 10.11.0&&< 10.27.0 | 10.27.0 |
| 📦npm | @sentry/google-cloud-serverless | ≥ 10.11.0&&< 10.27.0 | 10.27.0 |
| 📦npm | @sentry/nestjs | ≥ 10.11.0&&< 10.27.0 | 10.27.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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @sentry/node to 10.27.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6465-jgvq-jhgp 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 pinpoints whether GHSA-6465-jgvq-jhgp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-6465-jgvq-jhgp. 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-6465-jgvq-jhgp in your dependencies?
O3 detects GHSA-6465-jgvq-jhgp across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.