CISA Malcolm

Multiple security vulnerabilities have been identified in CISA's Malcolm platform, affecting versions up to v26.08.0. These flaws range from authentication bypasses and incorrect authorization to server-side request forgery and data amplification attacks. Specifically, issues with the nginx reverse proxy and the Arkime live capture service could allow unauthenticated attackers to gain administrative access or forge identities. Additionally, a CSRF vulnerability in the Flask application allows for the remote deletion of forensic logs, and a decompression flaw enables potential denial-of-service attacks via "gzip bombs."
Remediations are available through vendor updates, with fixes implemented in versions v26.08.0 and v26.09.0. Because Malcolm is utilized globally within critical infrastructure sectors—including energy and water systems—the potential impact of these vulnerabilities is significant. Recommended defensive measures include isolating control system networks behind firewalls and limiting internet exposure. No public exploitation of these vulnerabilities has been reported to CISA at this time.

CISA identified seven vulnerabilities in the Malcolm platform.
Affected versions include Malcolm v26.07.1 and v26.08.0.
Vulnerabilities include CVE-2026-107336, CVE-2026-107333, CVE-2026-107362, CVE-2026-107361, CVE-2026-107337, CVE-2026-107335, and CVE-2026-107334.
Vulnerability types are Authentication Bypass, Incorrect Authorization, Server-Side Request Forgery (SSRF), Cross-Site Request Forgery (CSRF), and Improper Handling of Highly Compressed Data.
Patches were released in versions v26.08.0 and v26.09.0.
Malcolm is deployed worldwide in Energy, Information Technology, and Water and Wastewater Systems sectors.
The company headquarters is located in the United States.
Seth Grover and the Idaho National Laboratory reported the vulnerabilities.
Initial publication of the notification occurred on 2026-10-07.
Revision 2 was published on 2026-10-15.

The strongest version of this narrative is a transparent, technical disclosure designed to protect critical infrastructure by providing precise version numbers and remediation paths. It serves as a textbook example of coordinated vulnerability disclosure, prioritizing the safety of the energy and water sectors over the reputation of the software.
The technical nature of the disclosure avoids typical manipulation; it provides specific CVEs and CWEs rather than vague threats. It describes the "how" of the vulnerabilities—such as case-insensitive regex matchers and percent-encoding bypasses—which allows security professionals to verify the claims independently.
Patterns detected: none
The root cause here is the inherent complexity of "glue" software. Malcolm integrates several powerful tools (Arkime, Zeek, OpenSearch, nginx, Flask). The vulnerabilities primarily emerge at the interfaces—the points where one tool hands off a request to another. This echoes a historical pattern in cybersecurity where the security posture of a system is not the sum of its secure parts, but is instead defined by the weakest link in the integration logic.
The implication is a reminder that "out-of-the-box" security configurations often fail when custom proxy layers are added. The cost is borne by the operators of critical infrastructure who must now perform emergency updates. However, the benefit is the reinforcement of the "defense-in-depth" paradigm: the vulnerabilities are severe, but their impact is neutralized if the system is properly isolated from the public internet.
Bridge Questions:
1. If these vulnerabilities existed in a proprietary commercial product rather than an open-source CISA tool, would the disclosure have been as granular?
2. How many other "integrated" security platforms harbor similar normalization inconsistencies between their proxy and backend layers?
Counterstrike Scan: A bad actor pushing this narrative would focus on the "critical infrastructure" and "worldwide" deployment to create panic and drive users toward a specific "hardened" alternative. This content remains a clinical technical advisory; it does not match the attack pattern.