MediumGHSA-6465-jgvq-jhgpCVE-2025-65944

Sentry's sensitive headers are leaked when `sendDefaultPii` is set to `true`

Published 24 Nov 2025 · Updated 7 Aug 2026

Affected packages

@sentry/nodenpm
Affected
>=10.11.0 <10.27.0
Fixed in
10.27.0
Update to the fixed version for your release line, for example:npm install @sentry/node@10.27.0
@sentry/astronpm
Affected
>=10.11.0 <10.27.0
Fixed in
10.27.0
Update to the fixed version for your release line, for example:npm install @sentry/astro@10.27.0
@sentry/aws-serverlessnpm
Affected
>=10.11.0 <10.27.0
Fixed in
10.27.0
Update to the fixed version for your release line, for example:npm install @sentry/aws-serverless@10.27.0
@sentry/bunnpm
Affected
>=10.11.0 <10.27.0
Fixed in
10.27.0
Update to the fixed version for your release line, for example:npm install @sentry/bun@10.27.0
@sentry/google-cloud-serverlessnpm
Affected
>=10.11.0 <10.27.0
Fixed in
10.27.0
Update to the fixed version for your release line, for example:npm install @sentry/google-cloud-serverless@10.27.0
@sentry/nestjsnpm
Affected
>=10.11.0 <10.27.0
Fixed in
10.27.0
Update to the fixed version for your release line, for example:npm install @sentry/nestjs@10.27.0
@sentry/nextjsnpm
Affected
>=10.11.0 <10.27.0
Fixed in
10.27.0
Update to the fixed version for your release line, for example:npm install @sentry/nextjs@10.27.0
@sentry/node-corenpm
Affected
>=10.11.0 <10.27.0
Fixed in
10.27.0
Update to the fixed version for your release line, for example:npm install @sentry/node-core@10.27.0
@sentry/nuxtnpm
Affected
>=10.11.0 <10.27.0
Fixed in
10.27.0
Update to the fixed version for your release line, for example:npm install @sentry/nuxt@10.27.0
@sentry/remixnpm
Affected
>=10.11.0 <10.27.0
Fixed in
10.27.0
Update to the fixed version for your release line, for example:npm install @sentry/remix@10.27.0
@sentry/solidstartnpm
Affected
>=10.11.0 <10.27.0
Fixed in
10.27.0
Update to the fixed version for your release line, for example:npm install @sentry/solidstart@10.27.0
@sentry/sveltekitnpm
Affected
>=10.11.0 <10.27.0
Fixed in
10.27.0
Update to the fixed version for your release line, for example:npm install @sentry/sveltekit@10.27.0

Details

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:

1. Their Sentry SDK configuration has sendDefaultPii set to true 2. Their application uses one of the Node.js Sentry SDKs with version from 10.11.0 to 10.26.0 inclusively:

  • @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

Is GHSA-6465-jgvq-jhgp in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected @sentry/node, and gives you the command that fixes it.

Scan a project free, no signupOr connect GitHub to scan every repo

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.