deniz.in

Markets

Weather

Loading weather

· via dev.to (home feed)

Open-source SOC platform AiSOC patches five flaws, including a CVSS 9.0 command injection

A dev.to disclosure details five AiSOC vulnerabilities, led by a CVSS 9.0 command injection that turns CrowdStrike response actions into SYSTEM-level code execution. All five are fixed in version 12.0.0.

Open-source SOC platform AiSOC patches five flaws, including a CVSS 9.0 command injection

Five security vulnerabilities in AiSOC, an open-source platform for running a security operations center, were disclosed in a post on dev.to on 30 September 2026, with a fuller breakdown published on ThreatAft's site. The most serious of the set, CVE-2026-103056, carries a CVSS score of 9.0 and allows arbitrary command execution on the endpoints the platform manages. All five issues are resolved in AiSOC 12.0.0, and the disclosure urges anyone running version 5.1.0 or newer to upgrade immediately.

The CVSS 9.0 command injection

According to the disclosure, the critical flaw sits in the code that assembles CrowdStrike Real Time Response commands. AiSOC splices four user-controllable parameters — file_path, path, script_name and script_args — into the command string without escaping them first. Injecting a single quotation mark into any of those values is enough to break out of the intended command and append attacker-chosen instructions.

The blast radius is what makes the bug severe rather than merely untidy: Real Time Response actions run on managed endpoints with SYSTEM privileges on Windows or root on Linux. An attacker who reaches the injection point can therefore execute code at the highest privilege level on the hosts the platform is meant to defend, turning the containment tooling itself into the delivery mechanism.

The other four flaws

The remaining vulnerabilities cluster around authentication and tenancy:

  • CVE-2026-103055 (CVSS 7.5) — the realtime WebSocket and SSE layer signs its tokens with a hard-coded JWT secret. Since that secret ships with the software, anyone can mint valid tokens and read live alerts and incident streams belonging to other tenants.
  • CVE-2026-103054 (CVSS 7.1) — authenticated users can claim tenants they do not own and browse those tenants' security data. The disclosure frames this as an MSSP tenant takeover scenario, which is most relevant to managed service providers running multi-tenant deployments.
  • CVE-2026-103053 (no CVSS score given in the post) — the endpoint that dispatches response actions ships without authentication in the default Docker Compose deployment. AISOC_DEV_MODE defaults to enabled, and in that configuration the service token is never generated, so the host-isolation endpoint accepts requests without any credentials.
  • CVE-2026-103057 (CVSS 4.3) — internal realtime event endpoints accept unauthenticated writes.

What operators should do

Beyond upgrading to 12.0.0, the disclosure's mitigation checklist calls for setting the AISOC_ACTIONS_SERVICE_TOKEN and AISOC_REALTIME_JWT_SECRET environment variables and switching off AISOC_DEV_MODE. Those settings directly address the two worst configuration problems: the dispatch endpoint that currently answers without credentials, and the shared JWT secret behind the realtime layer. ThreatAft's writeup pairs a root-cause analysis of each flaw with the checklist. The dev.to post scopes its advice to installations on 5.1.0 or later and does not state whether older releases are affected.

Why it matters

Security tooling is itself attack surface, and a SOC platform is a concentrated form of it. AiSOC holds the credentials needed to drive endpoint response actions, so a flaw in how it builds those commands hands an attacker the highest privileges available in the environment — the defenders' own. The low bar for triggering it, a single quote in a request parameter, leaves little room for assuming the flaw went unnoticed before publication.

The set also illustrates two recurring hazards for self-hosted open source: privileged defaults that trade safety for convenience, such as a development mode enabled out of the box and a service token that is never generated, and baked-in secrets shared across every installation. For MSSPs in particular, the cross-tenant reading flaws mean one vulnerable instance can expose other customers' incident data. Operators running AiSOC should treat the 12.0.0 upgrade, plus the token and secret changes, as a same-day task rather than routine maintenance.

  • #security
  • #vulnerabilities
  • #open-source
  • #soc
  • #edr

Related posts