CVE-2026-111883: Locust through 2.46.7 CSRF via Web UI /stop and /stats/reset

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-11 15:49 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

Locust through 2.46.7 contains a cross-site request forgery vulnerability that allows remote attackers to stop load tests or reset statistics via GET requests to /stop and /stats/reset. Attackers can lure an operator to a malicious page triggering cross-site GET requests, terminating running swarms and wiping recorded performance results.

Description quoted from the CVE record (assigned by VulnCheck, published 2026-10-19).

Weakness: Cross-Site Request Forgery (CSRF)

How it can be exploited

Exploitable over the network with low attack complexity with no special attack requirements needing no privileges and a user must take an action. Impact: confidentiality none, integrity low, availability low. CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N

CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: no. Technical impact: partial.

Public exploit evidence (Exploit Observer)

Exploit Observer found 3 code repositories naming this CVE.

Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.

See all 6 references on Exploit Observer

Live scores

EPSS
0.002
low predicted chance of attack
VEDAS
0.985
strong exploit evidence
On CISA KEV
Not listed
Detection rule
Suricata

Who is affected

ProductAffectedNot affected
locustio locustup to and including 2.46.7Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

Vendor guidance:

How to detect it

Suricata rules (network detection)

2 rules that alert on traffic matching this exploit: VEDAS CVE-2026-111883 Locust - CSRF Load Test Stop via GET /stop. Add them to your Suricata rule set and reload.

Show the rules
suricata
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-111883 Locust - CSRF Load Test Stop via GET /stop"; flow:established,to_server; http.method; content:"GET"; http.uri; content:"/stop"; nocase; fast_pattern; pcre:"/^\/stop(?:\?|$)/"; classtype:web-application-attack; reference:cve,CVE-2026-111883; reference:url,https://www.exploit.observer/?keyword=CVE-2026-111883&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=locust&match=exact; sid:1085405; rev:1;)
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-111883 Locust - CSRF Statistics Reset via GET /stats/reset"; flow:established,to_server; http.method; content:"GET"; http.uri; content:"/stats/reset"; nocase; fast_pattern; pcre:"/^\/stats\/reset(?:\?|$)/"; classtype:web-application-attack; reference:cve,CVE-2026-111883; reference:url,https://www.exploit.observer/?keyword=CVE-2026-111883&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=locust&match=exact; sid:1085406; rev:1;)

CVE-2026-111883.rules on GitHub

References

Vendor advisories and patches

Technical analysis and advisories

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.

Supporting partners

Feasible SecurityAskealGoTrust