CVE-2025-65944: Sentry Node.js SDK Sensitive Header Leakage
Summary
CVE-2025-65944: Sentry's sensitive headers are leaked when sendDefaultPii is set to true. Affects @sentry/node versions >= 10.11.0, < 10.27.0. Fixed in 10.27.0. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The Sentry SDK for Node.js is a powerful tool that helps developers monitor and fix crashes in their applications. It provides real-time error tracking and performance monitoring, allowing developers to gain insights into their application's health. However, a vulnerability has been identified in versions 10.11.0 to 10.26.0, where sensitive HTTP headers can be inadvertently sent to Sentry if the configuration option 'sendDefaultPii' is enabled.
Vulnerability Detail
The vulnerability arises when the Sentry SDK is configured with 'sendDefaultPii: true'. This configuration can lead to the unintentional transmission of sensitive HTTP headers, such as the 'Cookie' header, to Sentry's servers. These headers may contain sensitive information that could be exploited by unauthorized users to impersonate or escalate privileges within the application. The issue affects multiple Sentry SDK packages for Node.js, making it critical for users to assess their configurations and the potential exposure of sensitive data.
How To Fix
Latest published version: 11.8.0 as of 23 Oct 2026
npm install @sentry/node@11.8.0Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
10.27.0
This is the first release that contains the fix.
npm install @sentry/node@10.27.0Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
If upgrading is not immediately possible, users can mitigate the risk by setting 'sendDefaultPii: false' in their Sentry SDK configuration. This can be done as follows:
const Sentry = require('@sentry/node');
Sentry.init({
dsn: 'YOUR_DSN',
sendDefaultPii: false
});
Conclusion
In summary, the vulnerability CVE-2025-65944 in the Sentry Node.js SDK can lead to the unintended exposure of sensitive HTTP headers. Users are strongly advised to upgrade to version 10.27.0 or later to mitigate this risk. If an immediate upgrade is not feasible, disabling the 'sendDefaultPii' option serves as a temporary workaround.
See every vulnerability recorded for @sentry/node →
FAQ
The vulnerability can lead to the exposure of sensitive HTTP headers, including cookies, which could be exploited by unauthorized users.
You can check by visiting the Explore section in Sentry, navigating to Traces, and searching for 'http.request.header.authorization' or 'http.request.header.cookie'.
The affected versions are from 10.11.0 to 10.26.0 of various Sentry SDK packages for Node.js.
Yes, Vulert can monitor and alert in real-time for open-source vulnerabilities using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
References
Related vulnerabilities
Recent vulnerabilities recorded for @sentry/node.
