CVE-2024-40647: getsentry sentry-python · Information Exposure
Affects getsentry sentry-pythonSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 2.8.0 when convenient.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.8.0
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 1 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade sentry-sdk to 2.8.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
PyPIsentry-sdkpkg:pypi/sentry-sdkOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in sentry-python SDK version 2.8.0. Users should upgrade to version 2.8.0 or later to resolve this vulnerability. If upgrading is not possible, users can mitigate the risk by disabling all default integrations in the SDK to prevent environment variables from being passed to subprocesses. There is no indication that the vulnerability is mitigated by default or that no action is required.
Description
sentry-sdk is the official Python SDK for Sentry.io. A bug in Sentry's Python SDK < 2.8.0 allows the environment variables to be passed to subprocesses despite the `env={}` setting. In Python's `subprocess` calls, all environment variables are passed to subprocesses by default. However, if you specifically do not want them to be passed to subprocesses, you may use `env` argument in `subprocess` calls. Due to the bug in Sentry SDK, with the Stdlib integration enabled (which is enabled by default), this expectation is not fulfilled, and all environment variables are being passed to subprocesses instead. The issue has been patched in pull request #3251 and is included in sentry-sdk==2.8.0. We strongly recommend upgrading to the latest SDK version. However, if it's not possible, and if passing environment variables to child processes poses a security risk for you, you can disable all default integrations.
References
- github.com/getsentry/sentry-python/security/advisories/GHSA-g92j-qhmh-64v2 (opens in a new tab)
- github.com/getsentry/sentry-python/pull/3251 (opens in a new tab)
- github.com/getsentry/sentry-python/commit/763e40aa4cb57ecced467f48f78f335c87e9bdff (opens in a new tab)
- docs.python.org/3/library/subprocess.html (opens in a new tab)
- docs.sentry.io/platforms/python/integrations/default-integrations (opens in a new tab)
- docs.sentry.io/platforms/python/integrations/default-integrations/ (opens in a new tab)
- github.com/getsentry/sentry-python/releases/tag/2.8.0 (opens in a new tab)
- lists.debian.org/debian-lts-announce/2026/06/msg00001.html (opens in a new tab)