VulnerabilityPublished 10 Aug 2025Updated 13 Aug 2025

CVE-2025-8794: LitmusChaos Litmus · Authorization Bypass

Affects LitmusChaos LitmusSource CVE Database V5

Public exploit available · CVSS 4.8 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score

4.8Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Local
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
LitmusChaos Litmus	Affected 3.0 – 3.19.0 20 affected builds	Fixed in–

AI-suggested

First, restrict local access to systems running LitmusChaos to trusted personnel only, employing strict access control policies and network segmentation to limit exposure. Use host-based intrusion detection and monitoring to detect unusual access or manipulation of the LocalStorage Handler component or projectID parameters. Employ role-based access controls and audit logging within LitmusChaos environments to track and limit unauthorized actions. Consider running LitmusChaos in isolated or containerized environments with minimal privileges to reduce the attack surface. Regularly review and harden system configurations, and apply OS-level security best practices to prevent privilege escalation that could enable local access exploitation. Finally, monitor threat intelligence sources for any emerging exploits or patches related to CVE-2025-8794 and plan for rapid deployment once a fix becomes available.

Description

A vulnerability, which was classified as problematic, has been found in LitmusChaos Litmus up to 3.19.0. Affected by this issue is some unknown functionality of the component LocalStorage Handler. The manipulation of the argument projectID leads to authorization bypass. Local access is required to approach this attack. 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.

Impact

For European organizations, the impact of this vulnerability depends largely on the deployment context of LitmusChaos. Organizations using LitmusChaos for chaos engineering in development, testing, or production environments may face unauthorized access risks if internal access controls are weak. An attacker with local access could bypass authorization to manipulate or view project configurations, potentially disrupting chaos experiments or gaining insights into system resilience strategies. This could lead to indirect impacts on system availability or integrity if chaos experiments are tampered with maliciously. Additionally, unauthorized access to project data could expose sensitive operational details. Although the vulnerability requires local access, insider threats or compromised internal systems could exploit this flaw. Given the increasing adoption of chaos engineering in European tech sectors, especially in cloud-native and DevOps environments, this vulnerability could undermine trust in resilience testing processes and introduce risks to critical infrastructure or services relying on LitmusChaos. The medium severity rating suggests the threat is moderate but should not be ignored, particularly in regulated industries where data integrity and access controls are paramount.

Summary

CVE-2025-8794 is an authorization bypass vulnerability identified in the LitmusChaos Litmus platform, affecting all versions up to 3.19.0. The vulnerability resides in the LocalStorage Handler component, specifically involving the manipulation of the 'projectID' argument. By tampering with this argument, an attacker with local access can bypass authorization controls, potentially gaining unauthorized access to project-related resources or functionalities that should otherwise be restricted. The attack vector requires local access and low privileges, and no user interaction is necessary to exploit the flaw. The CVSS v4.0 score is 4.8, indicating a medium severity level, with the vector highlighting local attack vector (AV:L), low attack complexity (AC:L), no authentication required (AT:N), and low impact on confidentiality, integrity, and availability (VC:L, VI:L, VA:L). This suggests that while the exploit is feasible with local access, the overall impact on system security is limited but non-negligible, especially in environments where local access is not tightly controlled. The lack of vendor response and patch availability increases the risk for organizations relying on LitmusChaos for chaos engineering and resilience testing, as attackers could leverage this flaw to escalate privileges or access unauthorized project data within the platform.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 18 Aug 2025, 00:56 UTC

Technical details

References

Community reviews

Related threats