{"version":"2.1.248","anchor":"denylist-of-shell-startup-variables-added","canonical_anchor":"denylist-of-shell-startup-variables-added","heading":"Denylist of shell startup variables added","tier":"internal","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/denylist-of-shell-startup-variables-added","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Denylist of shell startup variables added\n\nA list names shell variables that can hijack a startup, with no visible consumer.\n\n**What**\n\nA standalone list of shell-sensitive environment variables now exists, covering `ENV`, `BASH_ENV`, `SHELLOPTS`, `PS4`, `GLOBIGNORE`, `LOCPATH`, `IFS`, `TMPDIR`, `BASH_LOADABLES_PATH` and others, the kind that can hijack a shell at startup. Whether Bash command handling filters them is not visible from the constant alone.\n\n**Evidence**\n\n`BASH_LOADABLES_PATH`\n\n- Area: Sandbox\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}