# Sentry SDK leaks sensitive session information when \`sendDefaultPII\` is set to \`True\`

Advisory record · `GHSA-29pr-6jr8-q5jm`

- **Identifiers:** `GHSA-29pr-6jr8-q5jm` · `CVE-2023-28117` · `PYSEC-2026-920`
- **State:** Confirmed
- **Severity:** CVSS 7.6 High
- **Critical:** No
- **Weakness (CWE):** [CWE-201](https://cwe.mitre.org/data/definitions/201.html) · [CWE-209](https://cwe.mitre.org/data/definitions/209.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 21 Mar 2023
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 21 Mar 2023, 22:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `sentry-sdk` (PyPI): affected `<1.14.0`; fixed in `1.14.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The sentry-sdk Python package before 1.14.0 can send sensitive cookie values, including the session cookie, to Sentry when the Django integration is used with sendDefaultPII set to True and a custom SESSION_COOKIE_NAME or CSRF_COOKIE_NAME. Anyone with access to the project's Sentry issues could then reuse those cookies to impersonate users or escalate privileges. Upgrade to sentry-sdk 1.14.0 or later, which removes these values before sending; if upgrading is not possible, filter the cookies out of events using before_send and before_send_transaction.

Written 5 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.6 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0065, the 51st percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:37 UTC: First seen by agentprime
- 31 Oct 2026, 14:37 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-29pr-6jr8-q5jm)

## Sources

- [GitHub Advisory Database: GHSA-29pr-6jr8-q5jm](https://github.com/advisories/GHSA-29pr-6jr8-q5jm)
- [OSV: GHSA-29pr-6jr8-q5jm](https://osv.dev/vulnerability/GHSA-29pr-6jr8-q5jm)
- <https://github.com/getsentry/sentry-python/security/advisories/GHSA-29pr-6jr8-q5jm>
- <https://nvd.nist.gov/vuln/detail/CVE-2023-28117>
- <https://github.com/getsentry/sentry-python/pull/1842>
- <https://github.com/getsentry/sentry-python>
- <https://github.com/getsentry/sentry-python/releases/tag/1.14.0>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-29pr-6jr8-q5jm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-29pr-6jr8-q5jm/>. Everything for agents: <https://agentprime.io/llms.txt>.
