cve.bz

CVE-2025-65944 getsentry sentry-javascript

5.1 mediumEPSS 0.4%Fix available

Medium (5.1) in getsentry sentry-javascript. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in @sentry/node 10.27.0.

On this page
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.

Severity

CVSS 4.0

5.1 medium
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:N/VA:N/SC:H/SI:L/SA:L
EPSS
0.4% (unchanged from 0.4% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 31st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-11-25. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-201 Insertion of Sensitive Information Into Sent Data
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • @sentry/node (npm): fixed in 10.27.0
  • @sentry/astro (npm): fixed in 10.27.0
  • @sentry/aws-serverless (npm): fixed in 10.27.0
  • @sentry/bun (npm): fixed in 10.27.0
  • @sentry/google-cloud-serverless (npm): fixed in 10.27.0
  • @sentry/nestjs (npm): fixed in 10.27.0
  • @sentry/nextjs (npm): fixed in 10.27.0
  • @sentry/node-core (npm): fixed in 10.27.0

Ask an AI about this CVE

Show the promptExplain CVE-2025-65944 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-65944?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-65944?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-65944 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
getsentry sentry-javascript>= 10.11.0, < 10.27.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-6465-jgvq-jhgpnpm@sentry/node>=10.11.0 <10.27.010.27.0
GHSA-6465-jgvq-jhgpnpm@sentry/astro>=10.11.0 <10.27.010.27.0
GHSA-6465-jgvq-jhgpnpm@sentry/aws-serverless>=10.11.0 <10.27.010.27.0
GHSA-6465-jgvq-jhgpnpm@sentry/bun>=10.11.0 <10.27.010.27.0
GHSA-6465-jgvq-jhgpnpm@sentry/google-cloud-serverless>=10.11.0 <10.27.010.27.0
GHSA-6465-jgvq-jhgpnpm@sentry/nestjs>=10.11.0 <10.27.010.27.0
GHSA-6465-jgvq-jhgpnpm@sentry/nextjs>=10.11.0 <10.27.010.27.0
GHSA-6465-jgvq-jhgpnpm@sentry/node-core>=10.11.0 <10.27.010.27.0
GHSA-6465-jgvq-jhgpnpm@sentry/nuxt>=10.11.0 <10.27.010.27.0
GHSA-6465-jgvq-jhgpnpm@sentry/remix>=10.11.0 <10.27.010.27.0
GHSA-6465-jgvq-jhgpnpm@sentry/solidstart>=10.11.0 <10.27.010.27.0
GHSA-6465-jgvq-jhgpnpm@sentry/sveltekit>=10.11.0 <10.27.010.27.0

Attack patterns (CAPEC)

  • CAPEC-12 Choosing Message Identifier Likelihood: High · Severity: High
  • CAPEC-217 Exploiting Incorrectly Configured SSL/TLS Likelihood: Low
  • CAPEC-612 WiFi MAC Address Tracking Severity: Low
  • CAPEC-613 WiFi SSID Tracking Severity: Low
  • CAPEC-618 Cellular Broadcast Message Request Severity: Low
  • CAPEC-619 Signal Strength Tracking Severity: Low
  • CAPEC-621 Analysis of Packet Timing and Sizes Severity: Low
  • CAPEC-622 Electromagnetic Side-Channel Attack Severity: Low
  • CAPEC-623 Compromising Emanations Attack Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON