Unintentional exposure of environment variables to subprocesses in sentry-sdk
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 5.3epss 0.2%
exploitation probability
0.2%top 90% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N
Affected products
getsentry · sentry-pythonReferences
https://docs.python.org/3/library/subprocess.htmlhttps://docs.sentry.io/platforms/python/integrations/default-integrationshttps://docs.sentry.io/platforms/python/integrations/default-integrations/#stdlibhttps://github.com/getsentry/sentry-python/commit/763e40aa4cb57ecced467f48f78f335c87e9bdffhttps://github.com/getsentry/sentry-python/pull/3251https://github.com/getsentry/sentry-python/releases/tag/2.8.0https://github.com/getsentry/sentry-python/security/advisories/GHSA-g92j-qhmh-64v2https://lists.debian.org/debian-lts-announce/2026/06/msg00001.html