How severe is GHSA-6465-jgvq-jhgp?

No CVSS score has been assigned to GHSA-6465-jgvq-jhgp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6465-jgvq-jhgp?

GHSA-6465-jgvq-jhgp affects the following packages: @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), and 4 more. Ecosystems affected: npm.

How do I fix GHSA-6465-jgvq-jhgp?

Update @sentry/node to 10.27.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6465-jgvq-jhgp is resolved across your whole dependency graph.

How do I detect GHSA-6465-jgvq-jhgp in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @sentry/node, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-6465-jgvq-jhgp if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-6465-jgvq-jhgp?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6465-jgvq-jhgp can be triaged on real exposure rather than presence alone.

Is GHSA-6465-jgvq-jhgp actively exploited in the wild?

No public exploit code has been indexed for GHSA-6465-jgvq-jhgp yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-6465-jgvq-jhgp?

GHSA-6465-jgvq-jhgp has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 28th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-6465-jgvq-jhgp?

GHSA-6465-jgvq-jhgp is classified as CWE-201 (CWE-201). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-6465-jgvq-jhgp published, and has it been updated?

GHSA-6465-jgvq-jhgp was published on November 24, 2025 and was last updated on August 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-6465-jgvq-jhgp — @sentry/node

Fix: getsentry/sentry-javascript#17475

GHSA-6465-jgvq-jhgp is a CWE-201 vulnerability in @sentry/node. A fix is available for @sentry/node — see the affected versions and patch details below.

Sentry's sensitive headers are leaked when `sendDefaultPii` is set to `true`

Also known asCVE-2025-65944

Published

Nov 24, 2025

Updated

Aug 7, 2026

Affected

12 pkgs

Patched

12 / 12

Exploits

None indexed

Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-6465-jgvq-jhgp.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs28th percentile — riskier than 28% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

12 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

3Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@sentry/nodenpm

25.0Mdownloads / week

@sentry/astronpm

137Kdownloads / week

@sentry/aws-serverlessnpm

473Kdownloads / week

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 sendDefaultPii set to true
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

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

Affected Packages

12 total 12 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@sentry/node`	≥ 10.11.0&&< 10.27.0	10.27.0`npm install @sentry/node@10.27.0`
📦npm	`@sentry/astro`	≥ 10.11.0&&< 10.27.0	10.27.0`npm install @sentry/astro@10.27.0`
📦npm	`@sentry/aws-serverless`	≥ 10.11.0&&< 10.27.0	10.27.0`npm install @sentry/aws-serverless@10.27.0`
📦npm	`@sentry/bun`	≥ 10.11.0&&< 10.27.0	10.27.0`npm install @sentry/bun@10.27.0`
📦npm	`@sentry/google-cloud-serverless`	≥ 10.11.0&&< 10.27.0	10.27.0`npm install @sentry/google-cloud-serverless@10.27.0`
📦npm	`@sentry/nestjs`	≥ 10.11.0&&< 10.27.0	10.27.0`npm install @sentry/nestjs@10.27.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @sentry/node, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @sentry/node to 10.27.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6465-jgvq-jhgp is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6465-jgvq-jhgp can be triaged on real exposure rather than presence alone.

Tailored to GHSA-6465-jgvq-jhgp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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:

O3 Security · Impact-Aware SCA

Is GHSA-6465-jgvq-jhgp in your dependencies?

O3 Security finds GHSA-6465-jgvq-jhgp across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works

CWE Classification

CWE-201CWE-201

Weaponization

No known public exploit tooling found.

OpenSSF Scorecard

Package health score