{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85513 exists.","fix":"No fix has been published for CVE-2026-85513 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-85513 is a medium-severity vulnerability in StackStorm st2, published on 4 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-85513 and fix it if it is affected.\n\nWhat it is: CVE-2026-85513 is a medium-severity vulnerability in StackStorm st2, published on 4 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85513 exists.\n\nAffected product: StackStorm st2. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-85513/ (Markdown: https://insights.sbomify.com/CVE-2026-85513/index.md)","id":"CVE-2026-85513","markdown":"https://insights.sbomify.com/CVE-2026-85513/index.md","name":"CVE-2026-85513","record":{"aliases":["GHSA-w6wr-mr8c-m255"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"StackStorm automation platform","requires_auth":"low_privilege","summary":"Remote attackers can escalate privileges in StackStorm st2 via improper privilege management in the NoOp RBAC backend, affecting default installations.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"},{"id":"CWE-266","name":"Incorrect Privilege Assignment"}],"description":"A weakness has been identified in StackStorm st2 up to 3.9.0. This issue affects the function assert_user_is_admin_if_user_query_param_is_provided of the file st2api/st2api/controllers/v1/actionexecutions.py of the component NoOp RBAC backend. This manipulation of the argument User causes improper privilege management. The attack is possible to be carried out remotely. The exploit has been made available to the public and could be used for attacks. Prior advisory CVE-2022-44009 was reported as a follow-up on the same sink, but this issue is distinct: it needs no Jinja RBAC und affects default install with RBAC disabled. The project was informed of the problem early through an issue report but has not responded yet.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"StackStorm st2 NoOp RBAC backend actionexecutions.py privileges management","id":"CVE-2026-85513","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"StackStorm st2 API Key auth.py privileges management","id":"CVE-2026-85514"},"packages":[],"prev":{"headline":"SourceCodester Class and Exam Timetabling System session.php authorization","id":"CVE-2026-85512"},"products":["st2"],"published":"2026-09-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-08","vendors":["StackStorm"]},"summary":"Remote attackers can escalate privileges in StackStorm st2 via improper privilege management in the NoOp RBAC backend, affecting default installations.","url":"https://insights.sbomify.com/CVE-2026-85513/"}