CVE-2025-65944: Node · Sentry's sensitive headers are leaked when `sendDefaultPii` is set to `true`
Affects @sentry/nodeSource GCVE Database
Not known to be exploited · CVSS 5.1 Medium : upgrade to 10.27.0 when convenient.
Data as of 19 Nov 2026, 02:47 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 5.1 |
|---|
- Patch
- Available – fixed in 10.27.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:N/VA:N/SC:H/SI:L/SA:LExploitation evidence
Disclosed: evidence found.
CVE published 25 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade @sentry/node and @sentry/astro and @sentry/aws-serverless and @sentry/bun and @sentry/google-cloud-serverless and @sentry/nestjs and @sentry/nextjs and @sentry/node-core and @sentry/nuxt and @sentry/remix and @sentry/solidstart and @sentry/sveltekit to 10.27.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npm@sentry/node | Affected
| Fixed in
|
| npm@sentry/astro | Affected
| Fixed in
|
| npm@sentry/aws-serverless | Affected
| Fixed in
|
| npm@sentry/bun | Affected
| Fixed in
|
| npm@sentry/google-cloud-serverless | Affected
| Fixed in
|
| npm@sentry/nestjs | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in Sentry JavaScript SDK version 10.27.0 and later. Users are strongly encouraged to upgrade to version 10.27.0 or newer. If upgrading is not immediately possible, users should set sendDefaultPii to false to prevent sensitive headers from being sent. This configuration change avoids the vulnerability by disabling the inclusion of personally identifiable information in traces.
Description
A vulnerability in Sentry's Node.js SDK versions 10.11.0 through 10.26.0 allows sensitive HTTP headers such as Authorization and Cookie to be leaked when the configuration option sendDefaultPii is set to true. This occurs because the SDK unintentionally includes these headers as trace span attributes, and Sentry's server-side scrubbing also fails to redact them due to shared matching logic. The issue is fixed in version 10.27.0.
References
- github.com/getsentry/sentry-javascript/security/advisories/GHSA-6465-jgvq-jhgp (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2025-65944 (opens in a new tab)
- github.com/getsentry/sentry-javascript/pull/17475 (opens in a new tab)
- github.com/getsentry/sentry-javascript/pull/18311 (opens in a new tab)
- github.com/getsentry/sentry-javascript/commit/a820fa2891fdcf985b834a5b557edf351ec54539 (opens in a new tab)
- github.com/getsentry/sentry-javascript (opens in a new tab)
- github.com/getsentry/sentry-javascript/releases (opens in a new tab)
- github.com/getsentry/sentry-javascript/releases/tag/10.11.0 (opens in a new tab)
- github.com/getsentry/sentry-javascript/releases/tag/10.27.0 (opens in a new tab)