pypi package report

Is sentry-sdk safe?

2 known vulnerabilities, worst severity HIGH.

// reach

52 direct dependencies

29 carry known advisories, worst CRITICAL

102 packages depend on it

an advisory here reaches each of them

Create a free accountfor every dependency path, dependent and what to upgrade
// ai model usage

No published models are known to use this package.


cvss
7.6
high

CVSS v3.1 base score out of 10

epss
0.65%
medium

chance of exploitation in 30 days, 51st percentile of all CVEs

xyz score
4.5
medium

CyberXYZ composite out of 10

fig. 01 — GHSA-29pr-6jr8-q5jm, the advisory selected below

// 2 advisories

GHSA-29pr-6jr8-q5jm

HIGHGitHub ratingCVE-2023-28117
// impact

When using the Django integration of the Sentry SDK in a specific configuration it is possible to leak sensitive cookies values, including the session cookie to Sentry. These sensitive cookies could then be used by someone with access to your Sentry issues to impersonate or escalate their privileges within your application.

The below must be true in order for these sensitive values to be leaked:

  • Your Sentry SDK configuration has sendDefaultPII set to True
  • You are using a custom name for either of the cookies below in your Django settings.
  • SESSION_COOKIE_NAME or
  • CSRF_COOKIE_NAME Django settings
  • You are not configured in your organization or project settings to use our data scrubbing features to account for the custom cookie names
// patches

As of version 1.14.0, the Django integration of the sentry-sdk will detect the custom cookie names based on your Django settings and will remove the values from the payload before sending the data to Sentry.

// workarounds

If you can not update your sentry-sdk to a patched version than you can use the SDKs filtering mechanism to remove the cookies from the payload that is sent to Sentry. For error events this can be done with the before_send callback method and for performance related events (transactions) you can use the before_send_transaction callback method.

If you'd like to handle filtering of these values on the server-side, you can also use our advanced data scrubbing feature to account for the custom cookie names. Look for the $http.cookies, $http.headers, $request.cookies, or $request.headers fields to target with your scrubbing rule.

// references// credits
// cvss v3.1 vector

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

Checked 2026-11-08 at 00:27 UTC. The most recent advisory here was published 2024-07-18. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.