Summary
CVE-2026-19179 is a high-severity injection vulnerability in IBM Financial Transaction Manager (FTM) for RedHat OpenShift that allows a remote, unauthenticated attacker to manipulate database queries via improper neutralization of special elements in a boolean expression (CWE-74). The flaw carries a CVSS v3.1 base score of 8.2 and primarily threatens the integrity of data processed by FTM, a platform used by financial institutions to manage transaction processing. IBM has released a fixed version and no workaround is available, so affected organizations should prioritize patching.
Technical details
- Root cause: FTM fails to properly neutralize special elements within a boolean expression before it is used in a database query, enabling attacker-controlled input to alter query logic (a form of injection classified under CWE-74).
- Trigger conditions: An attacker sends crafted network requests containing malicious boolean/query elements to a vulnerable FTM instance; no authentication or user interaction is required.
- Attack vector: Network-based (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N).
- Impact: High integrity impact — the attacker can manipulate underlying database queries, potentially altering transaction data or application logic; low availability impact; no direct confidentiality impact per the published CVSS vector.
Affected software
- IBM Financial Transaction Manager (FTM) for RedHat OpenShift, versions 4.0.6.0 through 4.0.10.0
Severity
- CVSS v3.1 Base Score: 8.2 (High)
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
Mitigation and recommended actions
- Immediate: Upgrade IBM Financial Transaction Manager for RedHat OpenShift to version 4.0.11.0 or later, which resolves this vulnerability.
- If patching cannot be performed immediately: IBM’s security bulletin does not list any workarounds or mitigations for this issue, so restricting network access to FTM management/application interfaces to trusted networks and closely monitoring database query logs for anomalous boolean-injection patterns is advised as a temporary compensating control until the patch can be applied.

