VDB
Sign up
LOW2.5

PYSEC-2026-1917

Sentry's Python SDK unintentionally exposes environment variables to subprocesses

Quick fix

PYSEC-2026-1917 — sentry-sdk: upgrade to the fixed version with the command below.

pip install --upgrade 'sentry-sdk>=1.45.1'

Details

### Impact

The bug in Sentry's Python SDK <2.8.0 results in the unintentional exposure of environment variables to subprocesses despite the `env={}` setting.

### Details

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, like in this example:

``` >>> subprocess.check_output(["env"], env={"TEST":"1"}) b'TEST=1\n' ```

If you'd want to not pass any variables, you can set an empty dict:

``` >>> subprocess.check_output(["env"], env={}) b'' ```

However, the bug in Sentry SDK <2.8.0 causes **all environment variables** to be passed to the subprocesses when `env={}` is set, unless the Sentry SDK's [Stdlib](https://docs.sentry.io/platforms/python/integrations/default-integrations/#stdlib) integration is disabled. The Stdlib integration is enabled by default.

### Patches The issue has been patched in https://github.com/getsentry/sentry-python/pull/3251 and the fix released in [sentry-sdk==2.8.0](https://github.com/getsentry/sentry-python/releases/tag/2.8.0). The fix was also backported to [sentry-sdk==1.45.1](https://github.com/getsentry/sentry-python/releases/tag/1.45.1).

### Workarounds

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, there are two options:

1. In your application, replace `env={}` with the minimal dict `env={"EMPTY_ENV":"1"}` or similar.

OR

2. Disable Stdlib integration: ``` import sentry_sdk

# Should go before sentry_sdk.init sentry_sdk.integrations._DEFAULT_INTEGRATIONS.remove("sentry_sdk.integrations.stdlib.StdlibIntegration")

sentry_sdk.init(...) ```

### References * Sentry docs: [Default integrations](https://docs.sentry.io/platforms/python/integrations/default-integrations/) * Python docs: [subprocess module](https://docs.python.org/3/library/subprocess.html) * Patch https://github.com/getsentry/sentry-python/pull/3251

Are you affected?

Enter the version of the package you're using.

Affected packages

PyPI/sentry-sdk
Introduced in: 0Fixed in: 1.45.1
Fixpip install --upgrade 'sentry-sdk>=1.45.1'

References