CVE-2021-44657: In StackStorm versions prior to 3.6.0, the jinja interpreter was not run in sandbox mode and thus allows execu

Q: How do I fix CVE-2021-44657?

stackstorm: upgrade to 3.6.0. Exact commands for each OS are on this page.

Q: Is CVE-2021-44657 being exploited?

CVE-2021-44657 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2021-44657 affect?

CVE-2021-44657 affects stackstorm. Severity is high (CVSS 8.8). 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 set

Q: How urgent is CVE-2021-44657?

Priority 57/100. High severity; Public exploit reference

This month

HIGH 8.8UPGRADE

CVE-2021-44657 is a high-severity flaw (CVSS 8.8) affecting stackstorm. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	2.6% (top 15%)
CISA exploited list	No
Published	2021-12-15
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: stackstorm

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2021-12-15 15:15 UTCPublished CVE record published
2026-06-17 04:12 UTCUpdated Record last modified

stackstorm stackstorm UPGRADE

Affected: < 3.6.0

Fixed in: 3.6.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy stackstorm || rpm -q stackstorm || stackstorm --version

2. UPGRADE to 3.6.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade stackstorm

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade stackstorm

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2021-44657?

stackstorm: upgrade to 3.6.0. Exact commands for each OS are on this page.

Is CVE-2021-44657 being exploited?

CVE-2021-44657 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2021-44657 affect?

CVE-2021-44657 affects stackstorm. Severity is high (CVSS 8.8). 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 set

How urgent is CVE-2021-44657?

Priority 57/100. High severity; Public exploit reference

Related CVEs

CVE-2022-44009 HIGH 7.5 DOWNGRADE Improper access control in Key-Value RBAC in StackStorm version 3.7.0 didn't check the permissions in Jinja fi
CVE-2022-43706 MEDIUM 5.4 UPGRADE Cross-site scripting (XSS) vulnerability in the Web UI of StackStorm versions prior to 3.8.0 allowed logged in
CVE-2021-28667 HIGH 7.5 UPGRADE StackStorm before 3.4.1, in some situations, has an infinite loop that consumes all available memory and disk

References

← Back to latest CVEs