A security vulnerability has been detected in StackStorm st2 up to 3.9.0. Impacted is an unknown function of the file st2api/st2api/controllers/v1/auth.py of the component API Key Handler. Such manipulation of the argument api_key_api.user leads to improper privilege management. The attack may be performed from remote. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report but has not responded yet.
CVE-2026-85514
Score 6.3 from GitHub Security Advisory (severity: LOW) published 2026-09-04. a secondary CVSS source baseline 6.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.3
- EG Score
- 6.3(high)
- EG Risk
- 44(Track)EG Risk 44/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity63% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 18%
- KEV
- Not listed
Published
September 4, 2026
Last Modified
September 4, 2026
Advisory Details (2)
Auto-updated Sep 4, 2026GitHub - StackStorm/st2: StackStorm (aka "IFTTT for Ops") is event-driven automation for auto-remediation, incident responses, troubleshooting, deployments, and more for DevOps and SREs. Includes rules engine, workflow, 160 integration packs with 6000+ actions (see https://exchange.stackstorm.org) and ChatOps. Installer at https://docs.stackstorm.com/install/index.html · GitHub
https://github.com/StackStorm/st2/API key creation allows a non-admin to bind a key to any user and gain that user's privileges (privilege escalation to admin) · Issue #6380 · StackStorm/st2 · GitHub
https://github.com/StackStorm/st2/issues/6380Vendor Advisories for CVE-2026-85514(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 19× in last 7d / 48× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-19 18:31 UTCEG score recompute
- 2026-09-19 18:31 UTCGHSA enrichment
- 2026-09-18 20:05 UTCEG score recompute
- 2026-09-18 20:05 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 21:38 UTCEG score recompute
- 2026-09-17 21:38 UTCGHSA enrichment
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-16 23:12 UTCEG score recompute
- 2026-09-16 23:12 UTCGHSA enrichment
- 2026-09-16 14:09 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-16 00:46 UTCEG score recompute
- 2026-09-16 00:46 UTCGHSA enrichment
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-15 02:20 UTCGHSA enrichment
- 2026-09-14 03:49 UTCEG score recompute
- 2026-09-14 03:49 UTCGHSA enrichment
- 2026-09-13 05:23 UTCEG score recompute
- 2026-09-13 05:23 UTCGHSA enrichment
- 2026-09-12 06:57 UTCEG score recompute
- 2026-09-12 06:57 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
Show 23 moreShow fewer
- 2026-09-11 08:31 UTCGHSA enrichment
- 2026-09-10 10:05 UTCEG score recompute
- 2026-09-10 10:05 UTCGHSA enrichment
- 2026-09-09 11:39 UTCEG score recompute
- 2026-09-09 11:39 UTCGHSA enrichment
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-08 13:13 UTCEG score recompute
- 2026-09-08 13:13 UTCGHSA enrichment
- 2026-09-07 14:44 UTCGHSA enrichment
- 2026-09-06 15:13 UTCEG score recompute
- 2026-09-06 15:13 UTCGHSA enrichment
- 2026-09-06 13:48 UTCEPSS rescore
- 2026-09-05 16:45 UTCEG score recompute
- 2026-09-05 16:45 UTCGHSA enrichment
- 2026-09-05 15:31 UTCEPSS rescore
- 2026-09-04 18:26 UTCNVD updateCVSS v4 → 2.1
- 2026-09-04 18:19 UTCEG score recompute
- 2026-09-04 18:19 UTCGHSA enrichment
- 2026-09-04 18:14 UTCMITRE cvelistV5CVSS v4 → 5.3
- 2026-09-04 13:27 UTCEG score recompute
- 2026-09-04 13:24 UTCNVD updateCVSS v4 → 2.1
- 2026-09-04 12:54 UTCEG score recompute
- 2026-09-04 12:53 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-85514?
When was CVE-2026-85514 disclosed?
Is CVE-2026-85514 actively exploited?
What is the CVSS score of CVE-2026-85514?
How do I remediate CVE-2026-85514?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-85514
Is Your Infrastructure Affected by CVE-2026-85514?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.