Skip to main content
CVE-2025-8795VulnerabilityPublished Updated

CVE-2025-8795: LitmusChaos Litmus · Improper Access Controls

Affects LitmusChaos LitmusSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 37% 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:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
LitmusChaos LitmusAffected
  • =3.0
  • =3.1
  • =3.2
  • =3.3
  • =3.4
  • =3.5
  • =3.6
  • =3.7
  • =3.8
  • =3.9
  • =3.10
  • =3.11
  • =3.12
  • =3.13
  • =3.14
  • =3.15
  • =3.16
  • =3.17
  • =3.18
  • =3.19.0
Fixed in–

AI-suggested

European organizations using LitmusChaos should immediately audit their deployments to identify affected versions (3.0 through 3.19.0). Until an official patch is released, organizations should implement strict network-level access controls to restrict access to the /auth/login endpoint, limiting it to trusted IP addresses or VPNs. Employing Web Application Firewalls (WAFs) with custom rules to detect and block anomalous projectID parameter manipulations can provide temporary protection. Monitoring and logging access to authentication endpoints should be enhanced to detect suspicious activities. Organizations should also consider isolating chaos engineering environments from production networks to reduce risk exposure. Regularly reviewing user permissions and applying the principle of least privilege within the platform can minimize potential damage. Finally, organizations should maintain close communication with LitmusChaos community channels for updates and patches, and prepare to apply fixes promptly once available.

Description

A vulnerability, which was classified as critical, was found in LitmusChaos Litmus up to 3.19.0. This affects an unknown part of the file /auth/login. The manipulation of the argument projectID leads to improper access controls. It is possible to initiate the attack 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.

References

Community reviews

Loading reviews…