Sentry vulnerable to stored Cross-Site Scripting (XSS) (CVE-2024-41656) | HOL Guard CVE

High · CVSS 7.1CVE-2024-41656GHSA-FM88-HC3V-3WWW

Sentry vulnerable to stored Cross-Site Scripting (XSS)

Answer in brief

CVE-2024-41656 records a High severity (CVSS 7.1) vulnerability in Sentry vulnerable to stored Cross-Site Scripting (XSS). The current sources do not mark it as known exploited. The current feed maps sentry (pypi). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Jul 23, 2024Updated Sep 10, 2026Source checked Sep 10, 2026First seen by HOL Sep 10, 2026Material review Sep 10, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 7.1
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 7.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps sentry (pypi). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
sentrypypi	>=10.0.0 <24.7.1	24.7.1

Recommended response

Check inventory. Check lockfiles and deployed manifests for sentry.
Review the reported fix. Update sentry to 24.7.1 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Jul 23, 2024
Evidence: source:osv:source_dates:source-dates:record
Source modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:record
First seen by HOL
Sep 10, 2026

Sources and claim methodology

Upstream source description

### Impact An unsanitized payload sent by an Integration platform integration allows the storage of arbitrary HTML tags on the Sentry side. This payload could subsequently be rendered on the Issues page, creating a Stored Cross-Site Scripting (XSS) vulnerability. This vulnerability might lead to the execution of arbitrary scripts in the context of a user’s browser. Self-hosted Sentry users may be impacted if untrustworthy Integration platform integrations send external issues to their Sentry instance. ### Patches The patch has been released in [Sentry 24.7.1](https://github.com/getsentry/self-hosted/releases/tag/24.7.1) ### Workarounds For Sentry SaaS customers, no action is needed. This has been patched on July 22, and even prior to the fix, the exploitation was not possible due to the strict Content Security Policy deployed on sentry.io site. For self-hosted users, we strongly recommend upgrading Sentry to the latest version. If it is not possible, you could [enable CSP on your self-hosted installation](https://develop.sentry.dev/self-hosted/csp/) with `CSP_REPORT_ONLY = False` (enforcing mode). This will mitigate the risk of XSS. ### References * Sentry Docs: [Integration platform / Create an External Issue](https://docs.sentry.io/api/integration/create-an-external-issue/) * Sentry Docs: [Self-hosted CSP](https://develop.sentry.dev/self-hosted/csp/) * The fix: https://github.com/getsentry/sentry/pull/74648 * PortSwigger: [Stored XSS](https://portswigger.net/web-security/cross-site-scripting/stored)

Quoted source text, attributed separately from HOL analysis.