GHSA-6465-jgvq-jhgp CVE-2025-65944
Sentry's sensitive headers are leaked when `sendDefaultPii` is set to `true`
- Severity
- 5.1 / 10
- Medium · CVSS 4.0
- Exploit chance (EPSS)
- 0.37%
- Chance of exploitation in the next 30 days. Higher than 30.77% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-201 Insertion of Sensitive Information Into Sent Data
- Fix
- Available
- 12 packages have a fixed version
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:
- Their Sentry SDK configuration has
sendDefaultPiiset totrue - Their application uses one of the Node.js Sentry SDKs with version from
10.11.0to10.26.0inclusively:
- @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 version.
Workarounds
Sentry strongly encourage customers to upgrade the SDK to the latest available version, 10.27.0 or later.
If it is not possible, consider setting sendDefaultPii: false to avoid unintentionally sending sensitive headers. See here for documentation.
Resources
- 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/pull/17475
- https://docs.sentry.io/platforms/javascript/guides/node/data-management/data-collected/#cookies
Affected versions
npm
| Package | Vulnerable | Fixed in |
|---|---|---|
| @sentry/astro | >= 10.11.0, < 10.27.0 |
10.27.0 |
| @sentry/astro | >= 10.11.0, < 10.27.0 |
10.27.0 |
| @sentry/aws-serverless | >= 10.11.0, < 10.27.0 |
10.27.0 |
| @sentry/aws-serverless | >= 10.11.0, < 10.27.0 |
10.27.0 |
| @sentry/bun | >= 10.11.0, < 10.27.0 |
10.27.0 |
| @sentry/bun | >= 10.11.0, < 10.27.0 |
10.27.0 |
| @sentry/google-cloud-serverless | >= 10.11.0, < 10.27.0 |
10.27.0 |
| @sentry/google-cloud-serverless | >= 10.11.0, < 10.27.0 |
10.27.0 |
| @sentry/nestjs | >= 10.11.0, < 10.27.0 |
10.27.0 |
| @sentry/nestjs | >= 10.11.0, < 10.27.0 |
10.27.0 |
| @sentry/nextjs | >= 10.11.0, < 10.27.0 |
10.27.0 |
| @sentry/nextjs | >= 10.11.0, < 10.27.0 |
10.27.0 |
| @sentry/node | >= 10.11.0, < 10.27.0 |
10.27.0 |
| @sentry/node | >= 10.11.0, < 10.27.0 |
10.27.0 |
| @sentry/node-core | >= 10.11.0, < 10.27.0 |
10.27.0 |
| @sentry/node-core | >= 10.11.0, < 10.27.0 |
10.27.0 |
| @sentry/nuxt | >= 10.11.0, < 10.27.0 |
10.27.0 |
| @sentry/nuxt | >= 10.11.0, < 10.27.0 |
10.27.0 |
| @sentry/remix | >= 10.11.0, < 10.27.0 |
10.27.0 |
| @sentry/remix | >= 10.11.0, < 10.27.0 |
10.27.0 |
| @sentry/solidstart | >= 10.11.0, < 10.27.0 |
10.27.0 |
| @sentry/solidstart | >= 10.11.0, < 10.27.0 |
10.27.0 |
| @sentry/sveltekit | >= 10.11.0, < 10.27.0 |
10.27.0 |
| @sentry/sveltekit | >= 10.11.0, < 10.27.0 |
10.27.0 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
@sentry/astro npm → 10.27.0
- npm
npm install @sentry/astro@10.27.0- yarn
yarn add @sentry/astro@10.27.0- pnpm
pnpm add @sentry/astro@10.27.0
@sentry/aws-serverless npm → 10.27.0
- npm
npm install @sentry/aws-serverless@10.27.0- yarn
yarn add @sentry/aws-serverless@10.27.0- pnpm
pnpm add @sentry/aws-serverless@10.27.0
@sentry/bun npm → 10.27.0
- npm
npm install @sentry/bun@10.27.0- yarn
yarn add @sentry/bun@10.27.0- pnpm
pnpm add @sentry/bun@10.27.0
@sentry/google-cloud-serverless npm → 10.27.0
- npm
npm install @sentry/google-cloud-serverless@10.27.0- yarn
yarn add @sentry/google-cloud-serverless@10.27.0- pnpm
pnpm add @sentry/google-cloud-serverless@10.27.0
@sentry/nestjs npm → 10.27.0
- npm
npm install @sentry/nestjs@10.27.0- yarn
yarn add @sentry/nestjs@10.27.0- pnpm
pnpm add @sentry/nestjs@10.27.0
@sentry/nextjs npm → 10.27.0
- npm
npm install @sentry/nextjs@10.27.0- yarn
yarn add @sentry/nextjs@10.27.0- pnpm
pnpm add @sentry/nextjs@10.27.0
@sentry/node npm → 10.27.0
- npm
npm install @sentry/node@10.27.0- yarn
yarn add @sentry/node@10.27.0- pnpm
pnpm add @sentry/node@10.27.0
@sentry/node-core npm → 10.27.0
- npm
npm install @sentry/node-core@10.27.0- yarn
yarn add @sentry/node-core@10.27.0- pnpm
pnpm add @sentry/node-core@10.27.0
@sentry/nuxt npm → 10.27.0
- npm
npm install @sentry/nuxt@10.27.0- yarn
yarn add @sentry/nuxt@10.27.0- pnpm
pnpm add @sentry/nuxt@10.27.0
@sentry/remix npm → 10.27.0
- npm
npm install @sentry/remix@10.27.0- yarn
yarn add @sentry/remix@10.27.0- pnpm
pnpm add @sentry/remix@10.27.0
@sentry/solidstart npm → 10.27.0
- npm
npm install @sentry/solidstart@10.27.0- yarn
yarn add @sentry/solidstart@10.27.0- pnpm
pnpm add @sentry/solidstart@10.27.0
@sentry/sveltekit npm → 10.27.0
- npm
npm install @sentry/sveltekit@10.27.0- yarn
yarn add @sentry/sveltekit@10.27.0- pnpm
pnpm add @sentry/sveltekit@10.27.0
Severity breakdown
CVSS 4.0 5.1
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
- Attack vector
- Network
- Attack complexity
- Low
- Attack requirements
- Present
- Privileges required
- High
- User interaction
- None
- Confidentiality (vulnerable system)
- None
- Integrity (vulnerable system)
- None
- Availability (vulnerable system)
- None
- Confidentiality (subsequent systems)
- High
- Integrity (subsequent systems)
- Low
- Availability (subsequent systems)
- Low
Weakness
CWE-201: Insertion of Sensitive Information Into Sent Data
The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.
How to prevent it
- Requirements: Specify which data in the software should be regarded as sensitive. Consider which types of users should have access to which types of data.
- Implementation: Ensure that any possibly sensitive data specified in the requirements is verified with designers to ensure that it is either a calculated risk or mitigated elsewhere. Any information that is not necessary to the functionality should be removed in order to lower both the overhead and the possibility of security sensitive data being sent.
- System Configuration: Setup default error messages so that unexpected errors do not disclose sensitive information.
- Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
References
Advisories
Fixes and patches
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-r5w7-f542-q2j4 Potential DoS when using ContextLines integration | Low | Also affects @sentry/astro |
| GHSA-wxxw-5cvc-53j7 Microsoft Security Advisory CVE-2026-66822 - .NET and Visual Studio Information Disclosure Vulnerability | Medium | Same weakness, CWE-201 |
| GHSA-g2v8-7jhw-pp8p Backstage: Sensitive information exposure in Scaffolder | Critical | Same weakness, CWE-201 |
| GHSA-238x-w2j9-gwwr Payload vulnerable to API key disclosure through ordinary document reads | High | Same weakness, CWE-201 |
| GHSA-p78m-89r6-pgf7 Open WebUI: A user's session cookies are sent to tool servers configured for bearer authentication | Medium | Same weakness, CWE-201 |
| GHSA-vx52-2968-3vc6 pnpm: Environment secrets exfiltrated via env-placeholder expansion in proxy settings read from an untrusted pnpm-workspace.yaml | High | Same weakness, CWE-201 |
| GHSA-955p-x3mx-jcvp Next.js: Unauthenticated disclosure of internal Server Function endpoints | Medium | Same weakness, CWE-201 |
| GHSA-rwj8-pgh3-r573 GitPython: Environment-variable exfiltration via os.path.expandvars() on Repo.clone_from() URL | High | Same weakness, CWE-201 |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor