CVE-2022-44009: Improper access control in Key-Value RBAC in StackStorm version 3.7.0 didn't check the permissions in Jinja fi

This month

HIGH 7.5REMOTEDOWNGRADE

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

Improper access control in Key-Value RBAC in StackStorm version 3.7.0 didn't check the permissions in Jinja filters, allowing attackers to access K/V pairs of other users, potentially leading to the exposure of sensitive Information.

Why this priority

High severity
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.6% (top 50%)
CISA exploited list	No
Weakness	CWE-862
Published	2022-12-06
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

2022-12-06 00:15 UTCPublished CVE record published
2026-06-17 05:07 UTCUpdated Record last modified

stackstorm stackstorm DOWNGRADE

Affected: 3.7.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.7.0

1. Check installed version

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

2. No fixed release: DOWNGRADE to a release before 3.7.0 (Debian / Ubuntu)

apt-cache madison stackstorm sudo apt install stackstorm=<VERSION_BEFORE_3.7.0> sudo apt-mark hold stackstorm

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list stackstorm sudo dnf downgrade stackstorm-<VERSION_BEFORE_3.7.0> sudo dnf versionlock add stackstorm

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

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-2022-44009?

stackstorm: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2022-44009 being exploited?

CVE-2022-44009 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-2022-44009 affect?

CVE-2022-44009 affects stackstorm. Severity is high (CVSS 7.5). Improper access control in Key-Value RBAC in StackStorm version 3.7.0 didn't check the permissions in Jinja filters, allowing attackers to access K/V pairs of other users, potentially leading to the exposure of sensitive Information.

How urgent is CVE-2022-44009?

Priority 44/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

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-44657 HIGH 8.8 UPGRADE In StackStorm versions prior to 3.6.0, the jinja interpreter was not run in sandbox mode and thus allows execu
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