# Sentry vulnerable to leaking superuser cleartext password in logs

Advisory record · `GHSA-6cjm-4pxw-7xp9`

- **Identifiers:** `GHSA-6cjm-4pxw-7xp9` · `CVE-2024-32474` · `PYSEC-2026-1911`
- **State:** Confirmed
- **Severity:** CVSS 7.3 High
- **Critical:** No
- **Weakness (CWE):** [CWE-117](https://cwe.mitre.org/data/definitions/117.html) · [CWE-312](https://cwe.mitre.org/data/definitions/312.html)
- **Tags:** [Other injection](https://agentprime.io/advisories/tag/injection.md) · [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 18 Apr 2024
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 18 Apr 2024, 18:22 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `sentry` (PyPI): affected `>=24.3.0, <24.4.1`; fixed in `24.4.1`

## Machine-written summary

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

> Sentry versions 24.3.0 up to but not including 24.4.1 write the superuser password in cleartext to logs when a superuser authenticates with a username and password on a self-hosted instance. An attacker who can read those logs could use the credentials to log in as a superuser. Self-hosted users should upgrade to Sentry 24.4.1 or later. As a workaround, set the logging level so that INFO logs are not generated and only WARNING and higher are recorded.

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.3 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0043, the 37th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:35 UTC: First seen by agentprime
- 31 Oct 2026, 14:35 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-6cjm-4pxw-7xp9)

## Sources

- [GitHub Advisory Database: GHSA-6cjm-4pxw-7xp9](https://github.com/advisories/GHSA-6cjm-4pxw-7xp9)
- [OSV: GHSA-6cjm-4pxw-7xp9](https://osv.dev/vulnerability/GHSA-6cjm-4pxw-7xp9)
- <https://github.com/getsentry/sentry/security/advisories/GHSA-6cjm-4pxw-7xp9>
- <https://nvd.nist.gov/vuln/detail/CVE-2024-32474>
- <https://github.com/getsentry/sentry/pull/66393>
- <https://github.com/getsentry/sentry/pull/69148>
- <https://github.com/getsentry/sentry/commit/d5b34568d9f1c41362ccb62141532a0a2169512f>
- <https://github.com/getsentry/sentry>

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-6cjm-4pxw-7xp9>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-6cjm-4pxw-7xp9/>. Everything for agents: <https://agentprime.io/llms.txt>.
