Vulnerabilities
Misconfiguration
Compliance
CVE Vulnerabilities

CVE-2026-9277

Improper Neutralization of Special Elements used in a Command ('Command Injection')

Published: May 22, 2026 | Modified: Jul 02, 2026
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
RedHat/V2
RedHat/V3
8.1 IMPORTANT
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Ubuntu
MEDIUM
Vulnerability-free packages from our partners
root.io logo minimus.io logo echo.ai logo
Additional information
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-9277
CWEhttps://cwe.mitre.org/data/definitions/77.html

shell-quotes quote() function did not validate object-token inputs against the operator model used by parse(). The .op field was backslash-escaped character by character using /(.)/g, which in JavaScript does not match line terminators (n, r, U+2028, U+2029). A line terminator in .op therefore passed through unescaped into the output; POSIX shells treat a literal newline as a command separator, so any content after it would execute as a second command. The vulnerable code path is reachable in two ways: (1) direct construction of { op: ...n... } from external input, and (2) via parse(cmd, envFn) when envFn returns object tokens whose .op is attacker-influenced. Both are documented API surface. Fixed by replacing the per-character escape with strict shape validation: .op must match the parsers control-operator allowlist; { op: glob, pattern } validates pattern and forbids line terminators; { comment } validates comment and forbids line terminators; any other object shape throws TypeError.

Weakness

The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.

Affected Software

NameVendorStart VersionEnd Version
Cryostat 4 on RHEL 9RedHatcryostat/cryostat-openshift-console-plugin-rhel9:4.2.0-10*
Cluster Observability Operator 1.5.0RedHatcluster-observability-operator/distributed-tracing-console-plugin-pf4-rhel9:1782840519*
Cluster Observability Operator 1.5.0RedHatcluster-observability-operator/distributed-tracing-console-plugin-pf5-rhel9:1782839981*
Cluster Observability Operator 1.5.0RedHatcluster-observability-operator/distributed-tracing-console-plugin-pf6-rhel9:1782839193*
Cluster Observability Operator 1.5.0RedHatcluster-observability-operator/distributed-tracing-console-plugin-rhel9:1782838753*
Cluster Observability Operator 1.5.0RedHatcluster-observability-operator/logging-console-plugin-pf4-rhel9:1782839279*
Cluster Observability Operator 1.5.0RedHatcluster-observability-operator/logging-console-plugin-pf5-rhel9:1782840539*
Cluster Observability Operator 1.5.0RedHatcluster-observability-operator/logging-console-plugin-rhel9:1782841925*
Cluster Observability Operator 1.5.0RedHatcluster-observability-operator/monitoring-console-plugin-pf5-rhel9:1782844225*
Cluster Observability Operator 1.5.0RedHatcluster-observability-operator/monitoring-console-plugin-pf6-rhel9:1782839658*
Cluster Observability Operator 1.5.0RedHatcluster-observability-operator/monitoring-console-plugin-rhel9:1782838476*
Cluster Observability Operator 1.5.0RedHatcluster-observability-operator/troubleshooting-panel-console-plugin-pf6-rhel9:1782839996*
Cluster Observability Operator 1.5.0RedHatcluster-observability-operator/troubleshooting-panel-console-plugin-rhel9:1782839494*
Red Hat Developer Hub 1.9RedHatrhdh/rhdh-hub-rhel9:1781187342*
Red Hat Developer Hub 1.9RedHatrhdh/rhdh-hub-rhel9:1782761244*
Red Hat Discovery 2RedHatdiscovery/discovery-ui-rhel9:1782166952*
Red Hat OpenShift Container Platform 4.21RedHatopenshift4/ose-console-rhel9:1782308675*
Red Hat OpenShift Container Platform 4.22RedHatopenshift4/ose-console-rhel9:1782224390*
Red Hat OpenShift Service Mesh 2.6RedHatopenshift-service-mesh/kiali-ossmc-rhel8:1780907585*
Red Hat OpenShift Service Mesh 2.6RedHatopenshift-service-mesh/kiali-rhel8:1780916536*
Red Hat OpenShift Service Mesh 3.0RedHatopenshift-service-mesh/kiali-ossmc-rhel9:1780470245*
Red Hat OpenShift Service Mesh 3.0RedHatopenshift-service-mesh/kiali-rhel9:1780916345*
Red Hat OpenShift Service Mesh 3.1RedHatopenshift-service-mesh/kiali-ossmc-rhel9:1780470706*
Red Hat OpenShift Service Mesh 3.1RedHatopenshift-service-mesh/kiali-rhel9:1780916478*
Red Hat OpenShift Service Mesh 3.2RedHatopenshift-service-mesh/kiali-ossmc-rhel9:1780470003*
Red Hat OpenShift Service Mesh 3.2RedHatopenshift-service-mesh/kiali-rhel9:1780916392*
Red Hat OpenShift Service Mesh 3.3RedHatopenshift-service-mesh/kiali-ossmc-rhel9:1780997382*
Red Hat OpenShift Service Mesh 3.3RedHatopenshift-service-mesh/kiali-rhel9:1780997438*
Red Hat Quay 3.10RedHatquay/quay-rhel8:1782487717*
Red Hat Quay 3.12RedHatquay/quay-rhel8:1781937357*
Red Hat Quay 3.9RedHatquay/quay-rhel8:1781878070*
Red Hat Satellite 6.18RedHatsatellite/iop-vulnerability-frontend-rhel9:1781032495*
Node-shell-quoteUbuntudevel*
Node-shell-quoteUbuntuesm-apps/bionic*
Node-shell-quoteUbuntuesm-apps/jammy*
Node-shell-quoteUbuntuesm-apps/noble*
Node-shell-quoteUbuntuesm-apps/resolute*
Node-shell-quoteUbuntujammy*
Node-shell-quoteUbuntunoble*
Node-shell-quoteUbuntuquesting*
Node-shell-quoteUbunturesolute*
Node-shell-quoteUbuntuupstream*

Extended Description

Many protocols and products have their own custom command language. While OS or shell command strings are frequently discovered and targeted, developers may not realize that these other command languages might also be vulnerable to attacks.

Potential Mitigations

  • Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
  • When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
  • Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.

References

Aqua Security is the largest pure-play cloud native security company, providing customers the freedom to innovate and run their businesses with minimal friction. The Aqua Cloud Native Security Platform provides prevention, detection, and response automation across the entire application lifecycle to secure the build, secure cloud infrastructure and secure running workloads wherever they are deployed.
Copyright © 2026 Aqua Security Software Ltd.   Privacy Policy | Terms of Use