Temporal Server compiles a Worker Controller Instance module, go.temporal.io/auto-scaled-workers, into its Worker Service, and that module registers a compute provider named k8s whose function is to manage workers running in a Kubernetes cluster. The k8s provider built its Kubernetes client from the client configuration supplied in the caller's request rather than from operator configuration, and building and using that client could run a command of the caller's choosing on the Worker Service host, under the account the server process runs as. Two frontend operations reach the provider. CreateWorkerDeploymentVersion requires a namespace write role. ValidateWorkerDeploymentVersionComputeConfig is registered as a read-only namespace operation, so an authenticated caller holding only a read role in a single namespace can reach the provider through it, and that route does not require a worker deployment to already exist. Execution happens while the submitted configuration is validated, so no scaling decision, task arrival, or unusual request sequence is required. Because the Worker Service process holds the persistence credentials for every namespace in the cluster and the cluster's TLS material, the consequence reaches beyond the caller's namespace to the cluster as a whole. The provider is present in the official temporal-server binaries and container images for the affected releases. The control that keeps it unreachable is the compute provider allowlist, the dynamic configuration setting workercontroller.compute_providers.enabled. On Temporal Server 1.31.0 through 1.31.2 that allowlist does not deny by default: when the setting is unset the check is skipped and every registered compute provider is permitted, k8s included, so a stock deployment of those releases is exposed. On 1.31.3 and later 1.31 releases, and on 1.32.0 and later 1.32 releases, the allowlist denies by default, and a deployment is exposed only where k8s has been added to it. The 1.30 release line does not include the Worker Controller Instance module and is unaffected. To determine whether a deployment is affected, check the following together. The deployed Temporal Server version is in an affected range. The Worker Service is running, which it is in the default service set and therefore in a stock deployment. The effective value of workercontroller.compute_providers.enabled contains k8s, or, on 1.31.0 through 1.31.2 only, is unset; check both the global value and every namespace-constrained override, because an override can add k8s for a single namespace. And authorization is configured, meaning a real authorizer and claim mapper are in place; a deployment running with no authorizer already grants every caller unrestricted access to every namespace, so it has no namespace boundary for this to cross. Deployments that use a custom authorizer should also check whether it permits ValidateWorkerDeploymentVersionComputeConfig to callers without namespace write access. The separate per-namespace dynamic configuration setting workercontroller.enabled does not gate the affected path on any affected release.
Improper neutralization of shell metacharacters in the timezone configuration field in certain Barracuda appliance products using common Barracuda code allows an authenticated administrator to inject OS commands that execute with root privileges when the crafted timezone value is subsequently processed.
Dell OpenManage Enterprise, versions prior to 4.8.0, contains an Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability. A low privileged attacker with adjacent network access could potentially exploit this vulnerability, leading to Command execution.
Zohocorp ManageEngine Eventlog Analyzer and ManageEngine Log360 versions before 13062 are vulnerable to Authenticated Remote Code Execution in Log Forward option.
Zohocorp ManageEngine Password Manager Pro versions before 13236 and PAM360 versions before 8601 are vulnerable to an authenticated Remote Code Execution vulnerability.
Improper Neutralization of Special Elements used in a Command ('Command Injection') in the Orchestrator component of SoftIron HyperCloud allows an authenticated user with access to the management plane to execute arbitrary operating system commands on hypervisor hosts as the privileged orchestration user. Attacker-controlled virtual machine template content (for example, the VM DESCRIPTION field) is delivered to hosts through a shell here-document whose terminator is not quoted, so shell expansion and here-document terminator injection are performed on that content during virtual machine lifecycle operations such as deploy, migrate, and network setup. Exploitation requires valid credentials, access to the management plane (owning a virtual machine alone is not sufficient), and a lifecycle operation that reaches the affected host. This issue affects the Orchestrator component of SoftIron HyperCloud from 1.0 through 2.6.17 and is fixed in 2.6.18.
ThingLinks is an enterprise IoT platform. Prior to 1.4.0, the `/groovyScriptTest/registerScript` endpoint accepts user-supplied Groovy script content and passes it to an unsandboxed `Groovy compilation and loading` flow. An authenticated attacker can provide code that is compiled and instantiated on the server, resulting in arbitrary server-side code execution. The issue affects the `rule engine`'s Groovy script test/register flow. This issue is fixed in version 1.4.0.
Pi-hole is a DNS sinkhole that protects devices from unwanted content without installing any client-side software. Prior to 6.5, advanced/Scripts/utils.sh getFTLPID() attempts to validate the pihole-owned /run/pihole-FTL.pid file with expr "${FTL_PID}" : "[^[:digit:]]", but this rejects only values whose first character is not a digit. An attacker with code execution as the pihole user can write a digit-prefixed arithmetic expression to the pihole-owned PID file. Root-run pihole subcommands then evaluate [[ "$pid" -eq "-1" ]], causing Bash to recursively evaluate array subscripts and execute command substitution as root. This bypasses the content-validation portion of the CVE-2026-41489 remediation while leaving its hardcoded PID-file path protection intact. This issue is fixed in version 6.5.
pgAdmin 4's Import/Export Data tool wraps a user's query export in a psql \copy (...) TO command and checks that the query's parentheses are balanced so that nothing can escape the wrapper. The check rejected a backslash inside a single-quoted string, but not inside a double-quoted identifier, where it treated the next double quote as closing the identifier. psql's \copy parser applies the connection's escape character to whichever quote opened a token, so with standard_conforming_strings off a backslash-escaped double quote does not close the identifier. pgAdmin's and psql's view of the quoting then diverged, a closing parenthesis hidden from the check ended the \copy (...) wrapper, and a following TO PROGRAM clause was executed by psql on the pgAdmin host, as the operating-system account running pgAdmin, before the server rejected the statement. An ordinary database role can turn standard_conforming_strings off for itself, and the Import/Export Data permission is granted to non-administrators by default.
This is a bypass of the fix for CVE-2026-17566. The fix rejects any backslash inside a double-quoted identifier, as was already done for single-quoted strings, since its meaning depends on a server setting that cannot be known reliably when the query is validated.
This issue affects pgAdmin 4: before 9.19.
Zuke-build versions prior to 1.51.0 contain an OS command injection vulnerability on Windows platforms. The issue arises because the tool launches Windows .cmd and .bat shims by prepending 'cmd /c', causing cmd.exe to reparse command lines with C-runtime quoting rules. If an attacker can influence the command line with unquoted metacharacters such as &, |, or ^, they can execute arbitrary commands in the build context with the same privileges and access to credentials. This vulnerability does not affect POSIX platforms and is fixed in version 1.51.0.
CVE-2026-118238 is an OS command injection vulnerability in the Tenda W18E router's web management server. It arises from improper validation of JSON fields in the 'diagnose' packet-capture feature, allowing an authenticated user to inject shell metacharacters into parameters that are used in a tcpdump command executed with root privileges. Notably, this vulnerability can be exploited without authentication if the device is in a factory-reset state. The vulnerability has a high severity with a CVSS score of 7.2.
Dell OpenManage Enterprise versions prior to 4.8.0 contain an OS Command Injection vulnerability (CWE-78) that allows a low privileged remote attacker to execute arbitrary commands. This vulnerability can lead to full compromise of confidentiality, integrity, and availability of the affected system. The issue is fixed in version 4.8.0 and later.
CallBackery versions before 0.62.0 for Perl contain an OS command injection vulnerability via sqlite3 shell commands in restored configuration backups. The restoreConfigBlob() function feeds a database dump from a backup to the sqlite3 command-line shell, which executes lines starting with a dot as shell commands. This allows an attacker who can supply a backup to execute arbitrary OS commands as the application user.
Dell OpenManage Enterprise versions prior to 4.8.0 contain an OS Command Injection vulnerability (CWE-78). This flaw allows a high privileged attacker with remote access to execute arbitrary commands on the affected system. The vulnerability is addressed in version 4.8.0 and later.
Dell OpenManage Enterprise versions prior to 4.8.0 contain an OS Command Injection vulnerability (CWE-78) that allows a high privileged remote attacker to execute arbitrary commands. This vulnerability has a CVSS score of 7.2, indicating high severity. The issue is fixed in version 4.8.0 and later.
Dell OpenManage Enterprise versions prior to 4.8.0 contain an OS Command Injection vulnerability (CWE-78) that allows a low privileged remote attacker to execute arbitrary commands. This vulnerability is addressed in version 4.8.0 and later.
CVE-2025-31704 is a critical OS command injection vulnerability in Dahua Intelligent Connection Center. A remote attacker can send specially crafted requests to execute arbitrary commands on the affected system, leading to remote code execution. The flaw affects versions from 1.000.0000000.1 through 1.000.0000005.0 and from 5.000.0000000.6 up to but not including 5.000.0000000.15. The vulnerability has a CVSS 3.1 score of 9.8, indicating high impact on confidentiality, integrity, and availability. A fix is available in version 5.000.0000000.15.
Improper Neutralization of Special Elements used in an OS Command ("OS Command Injection") vulnerability in Drupal Ffmpeg Image Toolkit allows OS Command Injection. This issue affects Ffmpeg Image Toolkit versions: from 0.0.0 to 1.0.3.
CVE-2026-119282 is an OS command injection vulnerability in the nrwl nx monorepo tool affecting certain versions of the @nx/maven and @nx/gradle plugins. The issue arises because project-graph analyzers launch shell commands that interpolate user-controlled plugin options, allowing command injection if the repository or pull request is attacker-controlled. This vulnerability allows an attacker to execute arbitrary commands with the privileges of the user running Nx. The flaw is fixed in nx versions 22.7.9 and 23.1.2 and corresponding plugin versions.
CVE-2026-115805 is an OS command injection vulnerability in Rapid7 Insight Agent on Linux and macOS. It arises from improper handling of local filesystem paths during inventory collection. An authenticated local user with existing access could exploit this flaw to gain elevated privileges. The vulnerability affects versions prior to 4.1.4.43 and has a high severity rating with a CVSS score of 7.8. A fix is available in version 4.1.4.43.