# CVE-2025-65944: @sentry/node — Fixed in 10.27.0 📦 npm Not in CISA KEV # CVE-2025-65944 — @sentry/node [Fix: getsentry/sentry-javascript@a820fa2](https://github.com/getsentry/sentry-javascript/commit/a820fa2891fdcf985b834a5b557edf351ec54539) CVE-2025-65944 is a CWE-201 vulnerability in @sentry/node. A fix is available for @sentry/node — see the affected versions and patch details below. Sentry-Javascript deals with leaked sensitive headers when \`sendDefaultPii\` is set to \`true\` Also known as[GHSA-6465-jgvq-jhgp](/vulnerability/GHSA-6465-jgvq-jhgp) Published Nov 25, 2025 Updated Oct 28, 2026 Affected 12 pkgs Patched 12 / 12 Exploits None indexed Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS) ## Exploitation Status ### No confirmed exploitation observed yet - CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment. Exploitation and automatability from CISA’s SSVC triage for CVE-2025-65944. ## EPSS Exploitation Probability [via FIRST.org ↗](https://www.first.org/epss/) 0.4%probability of exploitation in next 30 days Lower Risk0.00% Lower risk than most CVEs31th percentile — riskier than 31% of all scored CVEsHighest risk 0.00%0.29%0.58%0.87%0.1%0.4%May 26Sep 26Nov 26 Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/). ## Real-World Exposure 12 pkgs affected 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. 3Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream `@sentry/node`npm 55.3Mdownloads / week `@sentry/astro`npm 235Kdownloads / week `@sentry/aws-serverless`npm 1.1Mdownloads / week ## Description #### 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](https://github.com/getsentry/sentry-javascript/releases/tag/10.27.0) version. #### Workarounds Sentry strongly encourage customers to upgrade the SDK to the latest available version, [10.27.0](https://github.com/getsentry/sentry-javascript/releases/tag/10.27.0) or later. If it is not possible, consider setting `sendDefaultPii: false` to avoid unintentionally sending sensitive headers. See [here](https://docs.sentry.io/platforms/javascript/guides/node/#step-2-configure) for documentation. #### Resources - [https://develop.sentry.dev/sdk/expected-features/data-handling/#sensitive-data](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/releases/tag/10.11.0) - [https://github.com/getsentry/sentry-javascript/pull/17475](https://github.com/getsentry/sentry-javascript/pull/17475) - [https://docs.sentry.io/platforms/javascript/guides/node/data-management/data-collected/#cookies](https://docs.sentry.io/platforms/javascript/guides/node/data-management/data-collected/#cookies) ## Affected Packages 12 total 12 fixed Ecosystem Package Vulnerable range Fix 📦npm `@sentry/node` ≥ 10.11.0&&< 10.27.0 10.27.0`npm install @sentry/node@10.27.0` 📦npm `@sentry/astro` ≥ 10.11.0&&< 10.27.0 10.27.0`npm install @sentry/astro@10.27.0` 📦npm `@sentry/aws-serverless` ≥ 10.11.0&&< 10.27.0 10.27.0`npm install @sentry/aws-serverless@10.27.0` 📦npm `@sentry/bun` ≥ 10.11.0&&< 10.27.0 10.27.0`npm install @sentry/bun@10.27.0` 📦npm `@sentry/google-cloud-serverless` ≥ 10.11.0&&< 10.27.0 10.27.0`npm install @sentry/google-cloud-serverless@10.27.0` 📦npm `@sentry/nestjs` ≥ 10.11.0&&< 10.27.0 10.27.0`npm install @sentry/nestjs@10.27.0` ## Detection & mitigation playbook Open-source dependency 1. ### Detect 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. 2. ### Fix Update @sentry/node to 10.27.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-65944 is resolved across your whole dependency graph. 3. ### 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. ## Frequently Asked Questions \### 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: O3 Security · Impact-Aware SCA ### Is CVE-2025-65944 in your dependencies? Find it across npm, including transitive dependencies. [Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)