CVE-2026-71472: Acm-search-v2-rhel9: search-v2-operator: shell-command and sql injection in postgresql-start.sh via cr-supplied work_mem
A flaw was found in acm-search-v2-rhel9. This vulnerability allows an authenticated attacker, such as a hub administrator or a Search Custom Resource (CR) editor, to inject malicious shell commands or SQL statements. This occurs because the WORK_MEM string provided in the Search CR is not properly validated before being used in a bash script and an SQL query. Successful exploitation could lead to arbitrary code execution within the privileged postgres pod, potentially compromising the system.
Security readout for executives and security teams
Plain-English summary
An authenticated administrator or user permitted to edit Search resources can supply a malicious work_mem value. Because the operator passes it into shell and SQL contexts without adequate validation, the attacker could execute code inside a privileged PostgreSQL pod and potentially compromise the wider environment.
Executive priority
Treat as an urgent privileged-access vulnerability. Promptly inventory affected clusters, apply the applicable Red Hat advisory, and reduce Search CR editing rights meanwhile. Prioritize environments where many users hold hub-administrator or Search-editor permissions, because the vulnerable pod is privileged and successful exploitation may extend beyond the database workload.
Technical view
The search-v2-operator uses the Search Custom Resource WORK_MEM value in postgresql-start.sh and an SQL query without proper validation. This creates shell-command and SQL-injection paths. The CVSS 3.1 score is 9.1 because exploitation requires high privileges but may cross a security boundary and severely affect confidentiality, integrity, and availability.
Likely exposure
Exposure is limited to Red Hat Advanced Cluster Management 2.11 and 2.13 through 2.17 deployments using the listed rhacm2/acm-search-v2-rhel9 package versions. An attacker must already be a hub administrator or hold permission to edit Search Custom Resources. Internet reachability alone is not identified as sufficient.
Exploitation context
The supplied record is not in CISA KEV and provides no evidence of active exploitation. Exploitation requires authenticated, high-privilege access to influence the Search CR. Impact remains serious because successful injection could execute arbitrary code in a privileged PostgreSQL pod and potentially compromise the system.
Researcher notes
The supplied classification includes CWE-78 for OS command injection; the description also identifies SQL injection. The CVSS vector is AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H. Exact fixed package versions and detailed detection indicators are not included in the bundle, so consult the release-specific Red Hat advisories rather than inferring patch levels.
Mitigation direction
Identify affected RHACM deployments and the installed acm-search-v2-rhel9 package version.
Review and apply the Red Hat advisory appropriate to the deployed RHACM release.
Until updated, restrict Search Custom Resource editing to essential, trusted administrators.
Review vendor guidance before using any workaround not documented by Red Hat.
Validation and detection
Confirm whether RHACM 2.11 or 2.13 through 2.17 is deployed.
Compare the installed acm-search-v2-rhel9 package against the affected identifiers and applicable Red Hat advisory.
Review RBAC assignments granting creation or modification of Search Custom Resources.
Inspect Search resources for unexpected or suspicious work_mem values.
Review PostgreSQL pod and cluster audit logs for anomalous activity associated with Search changes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
5Timeline events
1ADP providers
9Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-78 · source CWE mapping
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.