{"version":"2.1.271","anchor":"env-var-sanitization-for-spawned-processes-reworked","canonical_anchor":"env-var-sanitization-for-spawned-processes-reworked","heading":"Env-var sanitization for spawned processes reworked","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/env-var-sanitization-for-spawned-processes-reworked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Env-var sanitization for spawned processes reworked\n\nEnvironment variables passed to spawned processes are filtered more thoroughly\n\n**Unclear.** The finding does not say which variables or sources are newly excluded, so the practical effect on any specific variable is unclear.\n\n**What**\n\nWhen Claude Code builds the environment variables for a process it spawns, it now runs an extra filtering pass over variable names that contain a dash, checking them against a lookup that ignores hyphen differences. It also pulls in additional sources of variables to exclude, beyond the fixed list it used before.\n\n**Why**\n\nThis broadens and tightens which environment variables get passed through to spawned processes, reducing the chance that an unwanted or sensitive variable leaks into a child process.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}