CVE-2025-8796: LitmusChaos Litmus · Missing Authorization
Affects LitmusChaos LitmusSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 33% 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:N/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: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), 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 compensating controls immediately. These include restricting network access to the LitmusChaos management interfaces to trusted IP ranges and enforcing strict authentication and authorization policies at the infrastructure level. Monitoring and logging all API calls to the /auth/delete_project/ endpoint can help detect suspicious activity. Organizations should consider deploying Web Application Firewalls (WAFs) with custom rules to block unauthorized delete requests or anomalous projectID manipulations. Regular backups of project configurations and data are essential to enable rapid restoration in case of unauthorized deletions. Additionally, organizations should isolate LitmusChaos environments from public networks and integrate multi-factor authentication (MFA) where possible to reduce the risk of credential compromise. Finally, maintaining close monitoring of vendor communications for patches or updates is critical.
Description
A vulnerability has been found in LitmusChaos Litmus up to 3.19.0 and classified as problematic. This vulnerability affects unknown code of the file /auth/delete_project/ of the component Delete Request Handler. The manipulation of the argument projectID leads to missing authorization. The attack can 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.