CVE-2024-41656
Sentry vulnerable to stored Cross-Site Scripting (XSS)
Sentry is an error tracking and performance monitoring platform. Starting in version 10.0.0 and prior to version 24.7.1, an unsanitized payload sent by an Integration platform integration allows storing arbitrary HTML tags on the Sentry side with the subsequent rendering them on the Issues page. Self-hosted Sentry users may be impacted in case of untrustworthy Integration platform integrations sending external issues from their side to Sentry. A patch has been released in Sentry 24.7.1. For Sentry SaaS customers, no action is needed. This has been patched on July 23, 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, the maintainers of Sentry strongly recommend upgrading Sentry to the latest version. If it is not possible, one could enable CSP on one's self-hosted installation with CSP_REPORT_ONLY = False (enforcing mode). This will mitigate the risk of cross-site scripting.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- Low
- User interaction
- Required
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Exploit likelihood
What each source reports
CVE List Score used
Sentry vulnerable to stored Cross-Site Scripting (XSS)
Sentry is an error tracking and performance monitoring platform. Starting in version 10.0.0 and prior to version 24.7.1, an unsanitized payload sent by an Integration platform integration allows storing arbitrary HTML tags on the Sentry side with the subsequent rendering them on the Issues page. Self-hosted Sentry users may be impacted in case of untrustworthy Integration platform integrations sending external issues from their side to Sentry. A patch has been released in Sentry 24.7.1. For Sentry SaaS customers, no action is needed. This has been patched on July 23, 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, the maintainers of Sentry strongly recommend upgrading Sentry to the latest version. If it is not possible, one could enable CSP on one's self-hosted installation with CSP_REPORT_ONLY = False (enforcing mode). This will mitigate the risk of cross-site scripting.
- Record
CVE-2024-41656- CVSS 3.1
- 7.1 High
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H - Weakness
- CWE-79
- Updated
- 2026-11-02
EUVDEUVD-2024-2337
Sentry is an error tracking and performance monitoring platform. Starting in version 10.0.0 and prior to version 24.7.1, an unsanitized payload sent by an Integration platform integration allows storing arbitrary HTML tags on the Sentry side with the subsequent rendering them on the Issues page. Self-hosted Sentry users may be impacted in case of untrustworthy Integration platform integrations sending external issues from their side to Sentry. A patch has been released in Sentry 24.7.1. For Sentry SaaS customers, no action is needed. This has been patched on July 23, 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, the maintainers of Sentry strongly recommend upgrading Sentry to the latest version. If it is not possible, one could enable CSP on one's self-hosted installation with CSP_REPORT_ONLY = False (enforcing mode). This will mitigate the risk of cross-site scripting.
- Record
EUVD-2024-2337- CVSS 3.1
- 7.1 High
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H - Updated
- 2026-11-03
GitHub AdvisoriesGHSA-fm88-hc3v-3www
Sentry vulnerable to stored Cross-Site Scripting (XSS)
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
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
- Record
GHSA-fm88-hc3v-3www- CVSS 3.1
- 7.1 High
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H - Weakness
- CWE-79, CWE-80
- Updated
- 2026-11-02
NVD
Sentry is an error tracking and performance monitoring platform. Starting in version 10.0.0 and prior to version 24.7.1, an unsanitized payload sent by an Integration platform integration allows storing arbitrary HTML tags on the Sentry side with the subsequent rendering them on the Issues page. Self-hosted Sentry users may be impacted in case of untrustworthy Integration platform integrations sending external issues from their side to Sentry. A patch has been released in Sentry 24.7.1. For Sentry SaaS customers, no action is needed. This has been patched on July 23, 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, the maintainers of Sentry strongly recommend upgrading Sentry to the latest version. If it is not possible, one could enable CSP on one's self-hosted installation with CSP_REPORT_ONLY = False (enforcing mode). This will mitigate the risk of cross-site scripting.
- Record
CVE-2024-41656- CVSS 3.1
- 7.1 High
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H - CVSS 3.1
- 5.4 Medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N - Weakness
- CWE-79
- Updated
- 2026-11-02
OSV
Sentry vulnerable to stored Cross-Site Scripting (XSS)
Sentry is an error tracking and performance monitoring platform. Starting in version 10.0.0 and prior to version 24.7.1, an unsanitized payload sent by an Integration platform integration allows storing arbitrary HTML tags on the Sentry side with the subsequent rendering them on the Issues page. Self-hosted Sentry users may be impacted in case of untrustworthy Integration platform integrations sending external issues from their side to Sentry. A patch has been released in Sentry 24.7.1. For Sentry SaaS customers, no action is needed. This has been patched on July 23, 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, the maintainers of Sentry strongly recommend upgrading Sentry to the latest version. If it is not possible, one could enable CSP on one's self-hosted installation with CSP_REPORT_ONLY = False (enforcing mode). This will mitigate the risk of cross-site scripting.
- Record
CVE-2024-41656- CVSS 3.1
- 7.1 High
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H - Weakness
- CWE-79
- Updated
- 2026-11-02
OSVGHSA-fm88-hc3v-3www
Sentry vulnerable to stored Cross-Site Scripting (XSS)
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
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
- Record
GHSA-fm88-hc3v-3www- CVSS 3.1
- 7.1 High
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H - Weakness
- CWE-79, CWE-80
- Updated
- 2026-11-02
OSVPYSEC-2026-1914
Sentry vulnerable to stored Cross-Site Scripting (XSS)
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
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
- Record
PYSEC-2026-1914- CVSS 3.1
- 7.1 High
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
sentryPyPI |
10.0.0 up to 24.7.1 | 24.7.1 |
sentryPyPI |
10.0.0 up to 24.7.1, plus listed versions 10.0.120.10.120.11.020.11.120.12.0 Show 45 moreShow less20.12.120.6.020.7.020.7.120.7.220.8.021.1.021.10.021.11.021.12.021.2.021.3.021.3.121.4.021.4.121.5.021.5.121.6.021.6.121.6.221.6.321.7.021.8.021.9.022.1.022.10.022.11.022.12.022.2.022.3.022.4.022.5.022.6.022.7.022.8.022.9.023.1.023.1.123.2.023.3.023.3.123.4.023.5.023.5.123.5.2 |
24.7.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2024-41656 is a high vulnerability (CVSS 7.1) in Getsentry Sentry, published July 23, 2024. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.47%, the 40th percentile. Fixed in sentry 24.7.1.
References
github.com/getsentry/sentry/security/advisories/GHSA-fm88-hc3v-3www
nvd.nist.gov/vuln/detail/CVE-2024-41656
pypi.org/project/sentry
Left out here: 5 versions. The JSON record has them.