HarborGuardharborguardDatabase
Back to search
CRITICALCVE-2026-34110Published Modified CNA VulnCheck

CVE-2026-34110: Guardian Language-System Unauthenticated OS Command Injection via id Parameter in complex_start.php

Guardian language-system passes the id GET parameter directly into a PHP exec() call in complex_start.php (line 14) without sanitization: exec(\"php jobs/complex.php \".$login_session.\" \".$_GET['id'].\" ...\"). No authentication is required. An unauthenticated remote attacker can append shell metacharacters to execute arbitrary OS commands on the server.

Metrics

CVSS v4.0
9.3
Severity
CRITICAL
Fixed in
Affected Products
1

Get notified

Email me when this CVE is updated: new fix versions, severity changes, or any record change.

HarborGuard Analysis

Synopsis

This is an OS command injection vulnerability in Guardian language-system, specifically in the complex_start.php script. The id GET parameter is passed directly into a PHP exec() call without any sanitization or authentication check, meaning an attacker can reach it over the network with no credentials at all. Successful exploitation gives the attacker arbitrary OS command execution on the server, with full read, write, and availability impact on the host. No fix version has been published yet; HarborGuard tracks the upstream advisory and will make a patched-image rebuild available the moment a fix is released.

HarborGuard Coverage

Detection

Detection of CVE-2026-34110 is available across every HarborGuard environment: the CVE is ingested from upstream feeds within minutes of publication and matched against all customer images in connected registries and CI/CD pipelines, including custom-built images derived from affected guardian language-system versions.

Available
Triage

HarborGuard scores this finding at CVSS 9.3 Critical and weights it against each environment's configured compliance policy, routing the alert to the appropriate team inbox within each customer organization based on image ownership and policy rules.

Available
Patch

Because no upstream fix version has been published, HarborGuard re-checks the advisory on every ingest cycle and will make a patched-image rebuild available automatically the moment the upstream project ships a corrected release. In the interim, the finding remains open and visible in each affected environment's vulnerability queue.

Pending upstream

Exploit Conditions

  • Network reachabilityRequired

    The vulnerable endpoint is exposed over the network; an attacker must be able to send HTTP requests to the server running guardian language-system.

  • AuthenticationNot required

    No authentication or session token is needed; the vulnerable complex_start.php script accepts requests from any unauthenticated caller.

  • Victim interactionNot required

    The attacker sends a crafted HTTP request directly to the server; no user action or social engineering is involved.

  • Attack complexityDetail

    Exploitation is reliable and condition-free; appending shell metacharacters to the id GET parameter is sufficient to inject and execute arbitrary commands.

Blast Radius

  • Attacker executes arbitrary OS commands on the server under the web process user, gaining an interactive foothold on the host.
  • All data readable by the web server process is exposed, including application source code, configuration files, and any stored credentials or secrets.
  • Attacker can write or overwrite files on the filesystem, enabling persistent backdoor installation or corruption of application data.
  • The host process can be terminated or the service disrupted, taking the affected application offline.

How HarborGuard Handles This

Available on HarborGuard: images containing the affected guardian language-system commit range are flagged at CVSS 9.3 Critical as soon as they appear in a connected registry or pipeline scan. Because no upstream fix exists at this time, HarborGuard monitors the advisory on every ingest cycle and will automatically queue a patched-image rebuild for environments with auto-remediation enabled the moment a fix is published upstream. While no patch is available, recommended compensating controls include placing the affected service behind a network policy that restricts inbound HTTP access to trusted sources only, applying egress filtering to limit outbound connections from the container, and disabling or gating the complex_start.php endpoint via application-level configuration if the feature is not required. The open finding remains surfaced in each environment's vulnerability queue with full CVSS detail until an upstream fix closes it.

See how HarborGuard automates this
Affected packages
  • guardian / language-system
    ≤ e42c395ec4b03fe62973a669c9209a673838b8a4
CVSS Vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N