Project takeover via client-trusted role response
Published Aug 10, 2025 · Updated Aug 13, 2025
Improper authorization in LitmusChaos Litmus 3.0 through 3.19.0 allows remote authenticated users to take over accessible projects. The web client accepts a role value from the /auth/list_projects response after it is changed from Viewer to Owner, rather than enforcing the server-assigned role for later actions. Viewer access to a project is required; successful exploitation grants owner-level actions, including changing project resources and deleting experiments.
Summary
What happened
Improper authorization in LitmusChaos Litmus 3.0 through 3.19.0 allows remote authenticated users to take over accessible projects. The web client accepts a role value from the /auth/list_projects response after it is changed from Viewer to Owner, rather than enforcing the server-assigned role for later actions. Viewer access to a project is required; successful exploitation grants owner-level actions, including changing project resources and deleting experiments.
The record
- CVE
- CVE-2025-8791
- Published
- Aug 10, 2025
- Updated
- Aug 13, 2025
- Vendor
- LitmusChaos
- Product
- Litmus
- Classifications
- CWE-285, CWE-266, T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 10, 2025CVE publishedPublication date reported by the CVE source.
- Aug 13, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.0
- Affected versionversion=3.1
- Affected versionversion=3.10
- Affected versionversion=3.11
- Affected versionversion=3.12
- Affected versionversion=3.13
- Affected versionversion=3.14
- Affected versionversion=3.15
- Affected versionversion=3.16
- Affected versionversion=3.17
- Affected versionversion=3.18
- Affected versionversion=3.19.0
- Affected versionversion=3.2
- Affected versionversion=3.3
- Affected versionversion=3.4
- Affected versionversion=3.5
- Affected versionversion=3.6
- Affected versionversion=3.7
- Affected versionversion=3.8
- Affected versionversion=3.9
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Privilege Escalation via Tampering with Role Value in Project Listing Responseproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo