CVE-2025-65944: getsentry sentry-javascript · Insertion of Sensitive Information Into Sent Data
Affects getsentry sentry-javascriptSource CVE Database V5
Not known to be exploited · CVSS 5.1 Medium · fixed in 10.27.0 : update getsentry sentry-javascript when convenient.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- 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
Weaponised: 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 26 Oct 2026.
What to do
AI-suggested
European organizations should immediately audit their usage of the Sentry-Javascript SDK in Node.js applications to identify versions between 10.11.0 and 10.27.0 with sendDefaultPii enabled. The primary mitigation is to upgrade all affected SDK instances to version 10.27.0 or later, where the vulnerability is patched. If upgrading is not immediately feasible, organizations should disable sendDefaultPii to prevent sensitive headers from being sent. Additionally, organizations must enforce strict access controls and multi-factor authentication on their Sentry organizations to prevent unauthorized access. Regularly reviewing and limiting Sentry organization membership to only trusted personnel reduces insider threat risk. Monitoring Sentry logs for unusual access patterns or data exports can help detect potential misuse. Finally, organizations should consider rotating session cookies and other sensitive tokens if exposure is suspected to mitigate the impact of any leaked credentials.
Description
Sentry-Javascript is an official Sentry SDKs for JavaScript. From version 10.11.0 to before 10.27.0, when a Node.js application using the Sentry SDK has sendDefaultPii: true it is possible to inadvertently send certain sensitive HTTP headers, including the Cookie header, to Sentry. Those headers would be stored within a Sentry organization as part of the associated trace. A person with access to the Sentry organization could then view and use these sensitive values to impersonate or escalate their privileges within the application. This issue has been patched in version 10.27.0.
References
- github.com/getsentry/sentry-javascript/security/advisories/GHSA-6465-jgvq-jhgp (opens in a new tab)
- github.com/getsentry/sentry-javascript/pull/17475 (opens in a new tab)
- github.com/getsentry/sentry-javascript/commit/a820fa2891fdcf985b834a5b557edf351ec54539 (opens in a new tab)
- github.com/getsentry/sentry-javascript/releases/tag/10.11.0 (opens in a new tab)