CVE-2024-41656

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 with CSP_REPORT_ONLY = False (enforcing mode). This will mitigate the risk of XSS.

References

• Sentry Docs: Integration platform / Create an External Issue
• Sentry Docs: Self-hosted CSP
• The fix: https://github.com/getsentry/sentry/pull/74648
• PortSwigger: Stored XSS

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.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2024-41656 has a CVSS score of 7.1 (High). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (24.7.1); upgrading removes the vulnerable code path.

Kodem intelligence

The patch has been released in Sentry 24.7.1

1. What is CVE-2024-41656? CVE-2024-41656 is a high-severity cross-site scripting (XSS) vulnerability in sentry (pip), affecting versions >= 10.0.0, < 24.7.1. It is fixed in 24.7.1. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2024-41656? CVE-2024-41656 has a CVSS score of 7.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of sentry are affected by CVE-2024-41656? sentry (pip) versions >= 10.0.0, < 24.7.1 is affected.
4. Is there a fix for CVE-2024-41656? Yes. CVE-2024-41656 is fixed in 24.7.1. Upgrade to this version or later.
5. Is CVE-2024-41656 exploitable, and should I be worried? Whether CVE-2024-41656 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-41656 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-41656? Upgrade sentry to 24.7.1 or later.