https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 05:16:39 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-261851 EUVD-2026-261851 https://cve.radiocsirt.org/vuln/euvd-2026-261851 https://cve.radiocsirt.org/vuln/fkie_cve-2025-65944 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-65944 https://cve.radiocsirt.org/vuln/ghsa-6465-jgvq-jhgp <p><strong>Affected:</strong> npm: @sentry/node, npm: @sentry/astro, npm: @sentry/aws-serverless, npm: @sentry/bun, npm: @sentry/google-cloud-serverless, npm: @sentry/nestjs, npm: @sentry/nextjs, npm: @sentry/node-core, npm: @sentry/nuxt, npm: @sentry/remix and 2 more</p> <p>### 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.</p> <p>Sentry’s server-side scrubbing (handled by Sentry&#39;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.</p> <p>Users may be impacted if:</p> <p>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</p> <p>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&#39; applications and configurations.</p> <p>### 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.</p> <p>### Workarounds Sentry strongly encourage cust…</p> <p><strong>Affected:</strong> npm: @sentry/node, npm: @sentry/astro, npm: @sentry/aws-serverless, npm: @sentry/bun, npm: @sentry/google-cloud-serverless, npm: @sentry/nestjs, npm: @sentry/nextjs, npm: @sentry/node-core, npm: @sentry/nuxt, npm: @sentry/remix and 2 more</p> <p>### 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.</p> <p>Sentry’s server-side scrubbing (handled by Sentry&#39;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.</p> <p>Users may be impacted if:</p> <p>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</p> <p>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&#39; applications and configurations.</p> <p>### 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.</p> <p>### Workarounds Sentry strongly encourage cust…</p> https://cve.radiocsirt.org/vuln/ghsa-6465-jgvq-jhgp