CVE-2025-8797: LitmusChaos Litmus · Permission Issues
Affects LitmusChaos LitmusSource CVE Database V5
Public exploit available · CVSS 5.3 Medium.
Data as of 26 Oct 2026, 12:55 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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:PExploitation evidence
Disclosed: evidence found.
CVE published 10 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LitmusChaos Litmus | Affected
| Fixed in– |
AI-suggested
Given the absence of an official patch, European organizations should implement the following specific mitigations: 1) Restrict network access to LitmusChaos components, especially the LocalStorage Handler, using Kubernetes network policies and firewall rules to limit exposure to trusted sources only. 2) Employ strict Role-Based Access Control (RBAC) within Kubernetes to minimize permissions granted to LitmusChaos components and users, ensuring the principle of least privilege is enforced. 3) Monitor and audit LitmusChaos logs and Kubernetes API server logs for unusual permission changes or unexpected chaos experiment modifications. 4) Consider isolating LitmusChaos deployments in dedicated namespaces or clusters to contain potential exploitation impact. 5) Temporarily disable or limit the use of LocalStorage Handler features if feasible until a patch is available. 6) Engage with the LitmusChaos community or maintainers for updates and potential workarounds. 7) Implement runtime security tools that can detect anomalous behavior in Kubernetes pods and containers related to LitmusChaos. These targeted mitigations go beyond generic advice by focusing on network segmentation, strict access controls, and monitoring tailored to the affected component and environment.
Description
A vulnerability was found in LitmusChaos Litmus up to 3.19.0 and classified as critical. This issue affects some unknown processing of the component LocalStorage Handler. The manipulation leads to permission issues. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.