7.6

CVE-2023-28117: Sentry SDK leaks sensitive session information when `sendDefaultPII` is set to `True`

Modified
AliasesGHSA-29pr-6jr8-q5jmPYSEC-2026-920UBUNTU-CVE-2023-28117
Published 22-03-2023Last modified 25-02-2025

Vulnerability summary

CVE-2023-28117 is a high (CVSS 7.6) vulnerability in getsentry sentry-python. EPSS estimates a 0.65% chance of exploitation in the next 30 days, higher than 51% of scored vulnerabilities.

Priority
Routine

Not severe (CVSS 7.6, network access); no exploitation reported by the 5 checked sources

Source freshness unavailable

How is this decided?
CVSS score
7.6/10
010
High · v3.1 (CVE.org)
EPSS score
0.65%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Timeline

  1. 22-03-2023
    PublishedVulnerability first disclosed.
  2. 25-02-2025
    Last modifiedVulnerability information updated.

Description

Sentry SDK is the official Python SDK for Sentry, real-time crash reporting software. When using the Django integration of versions prior to 1.14.0 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. In order for these sensitive values to be leaked, the Sentry SDK configuration must have `sendDefaultPII` set to `True`; one must use a custom name for either `SESSION_COOKIE_NAME` or `CSRF_COOKIE_NAME` in one's Django settings; and one must not be configured in one's organization or project settings to use Sentry's data scrubbing features to account for the custom cookie names. As of version 1.14.0, the Django integration of the `sentry-sdk` will detect the custom cookie names based on one's Django settings and will remove the values from the payload before sending the data to Sentry. As a workaround, use the SDK's 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) one can use the `before_send_transaction` callback method. Those who want to handle filtering of these values on the server-side can also use Sentry's 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 a scrubbing rule.

CVSS metrics

4 scores · 4 sources · 1 version

EPSS trend

Probability

0.65%

Chance of exploitation in the next 30 days

Percentile

51%

Versus all other CVEs

30-day change

No change 0.00 pp

From 0.65% on 04-10-2026

04-10-202603-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Version check

Known conditions: network-reachable, administrative account, no user interaction (CVSS vector). Other conditions: not stated in public data.

Getsentry1 product
PyPI1 product
  • sentry-sdk< 1.14.0
Sentry1 product
Ubuntu1 product
  • sentry-pythonAll versions (No fix recorded)

4 vendors · 4 products

References

9 links