Summary
Sentry's sensitive headers are leaked when sendDefaultPii is set to true
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
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.
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
The issue has been patched in all Sentry JavaScript SDKs starting from the 10.27.0 version.
Frequently Asked Questions
- What is CVE-2025-65944? CVE-2025-65944 is a medium-severity security vulnerability in @sentry/node (npm), affecting versions >= 10.11.0, < 10.27.0. It is fixed in 10.27.0.
- Which packages are affected by CVE-2025-65944?
@sentry/node(npm) (versions >= 10.11.0, < 10.27.0)@sentry/astro(npm) (versions >= 10.11.0, < 10.27.0)@sentry/aws-serverless(npm) (versions >= 10.11.0, < 10.27.0)@sentry/bun(npm) (versions >= 10.11.0, < 10.27.0)@sentry/google-cloud-serverless(npm) (versions >= 10.11.0, < 10.27.0)@sentry/nestjs(npm) (versions >= 10.11.0, < 10.27.0)@sentry/nextjs(npm) (versions >= 10.11.0, < 10.27.0)@sentry/node-core(npm) (versions >= 10.11.0, < 10.27.0)@sentry/nuxt(npm) (versions >= 10.11.0, < 10.27.0)@sentry/remix(npm) (versions >= 10.11.0, < 10.27.0)@sentry/solidstart(npm) (versions >= 10.11.0, < 10.27.0)@sentry/sveltekit(npm) (versions >= 10.11.0, < 10.27.0)
- Is there a fix for CVE-2025-65944? Yes. CVE-2025-65944 is fixed in 10.27.0. Upgrade to this version or later.
- Is CVE-2025-65944 exploitable, and should I be worried? Whether CVE-2025-65944 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 CVE-2025-65944 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 CVE-2025-65944?
- Upgrade
@sentry/nodeto 10.27.0 or later - Upgrade
@sentry/astroto 10.27.0 or later - Upgrade
@sentry/aws-serverlessto 10.27.0 or later - Upgrade
@sentry/bunto 10.27.0 or later - Upgrade
@sentry/google-cloud-serverlessto 10.27.0 or later - Upgrade
@sentry/nestjsto 10.27.0 or later - Upgrade
@sentry/nextjsto 10.27.0 or later - Upgrade
@sentry/node-coreto 10.27.0 or later - Upgrade
@sentry/nuxtto 10.27.0 or later - Upgrade
@sentry/remixto 10.27.0 or later - Upgrade
@sentry/solidstartto 10.27.0 or later - Upgrade
@sentry/sveltekitto 10.27.0 or later
- Upgrade