VulnerabilityPublished 10 Aug 2025Updated 13 Aug 2025

CVE-2025-8792: LitmusChaos Litmus · Client-Side Enforcement of Server-Side Security

Affects LitmusChaos LitmusSource CVE Database V5

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score

5.3Medium

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

EPSS: 1.0% chance of exploitation in 30 days – higher than 63% 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:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
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: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
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: None: There is no loss of confidentiality within 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: None: There is no impact to availability within 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

These include restricting network access to LitmusChaos management interfaces using firewall rules or network segmentation to limit exposure to trusted internal users only. Employ strict authentication and authorization mechanisms around LitmusChaos deployments to prevent unauthorized access. Monitor and audit all chaos engineering activities for anomalous or unexpected experiment configurations or executions. Consider temporarily disabling or isolating LitmusChaos components in critical environments until a vendor patch is released. Additionally, review and harden Kubernetes RBAC policies to minimize privileges granted to LitmusChaos service accounts. Organizations should also stay alert for vendor updates or community patches and plan prompt deployment once available.

Description

A vulnerability classified as problematic has been found in LitmusChaos Litmus up to 3.19.0. Affected is an unknown function. The manipulation leads to client-side enforcement of server-side security. It is possible to launch 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.

Impact

For European organizations, especially those leveraging cloud-native infrastructure and Kubernetes environments, this vulnerability poses a risk of unauthorized manipulation of chaos engineering experiments or related configurations. This could lead to unintended disruptions, integrity compromises, or bypass of security policies designed to safeguard production or staging environments. Organizations relying on LitmusChaos for resilience testing may face increased risk of operational instability or exposure of internal system behaviors. The medium severity indicates that while the vulnerability is not critical, exploitation could degrade trust in system integrity and impact service reliability. Given the remote exploitability and lack of required authentication, attackers could target European enterprises' development and testing environments, potentially escalating to broader operational impacts if chaos experiments are misused or manipulated maliciously.

Summary

CVE-2025-8792 is a medium-severity vulnerability affecting LitmusChaos Litmus versions up to 3.19.0. The vulnerability arises from improper enforcement of server-side security controls on the client side, allowing an attacker to bypass intended server-side restrictions by manipulating client-side mechanisms. This flaw can be exploited remotely without requiring user interaction or elevated privileges, making it accessible to unauthenticated attackers. The vulnerability's CVSS 4.0 base score is 5.3, reflecting a moderate impact primarily on the integrity of the system, with limited impact on confidentiality and availability. The attack vector is network-based with low attack complexity and no privileges or user interaction needed. The vulnerability does not involve scope or security requirements changes. Although the vendor was notified early, no response or patch has been issued, and no known exploits are currently observed in the wild. The lack of patch availability increases the risk for organizations using affected versions. LitmusChaos Litmus is a tool used for chaos engineering to test resilience in cloud-native environments, often integrated into Kubernetes clusters and CI/CD pipelines. The vulnerability could allow attackers to circumvent security controls, potentially leading to unauthorized actions or disruptions within these environments.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats