Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-18162 – Remote Code Execution – IBM Financial Transaction Manager (FTM) for RedHat OpenShif

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-18162 is a critical code injection vulnerability in IBM Financial Transaction Manager (FTM) for RedHat OpenShift. The flaw stems from improper neutralization of user-controlled input passed to a JavaScript Function constructor, allowing a remote, unauthenticated attacker to execute arbitrary code on the server. Given the 9.8 CVSS score and the network-facing attack vector, this issue poses a severe risk to financial institutions running affected FTM deployments.

Technical details

  • Root cause: User-supplied input is passed into a new Function(...) constructor call without proper sanitization, allowing attacker-controlled strings to be evaluated as executable JavaScript (CWE-94: Improper Control of Generation of Code).
  • Trigger conditions: An attacker sends a specially crafted request containing malicious code to an exposed FTM interface that ultimately reaches the vulnerable Function constructor logic.
  • Attack vector: Network-based; no authentication or user interaction is required to exploit the vulnerability.
  • Impact: Successful exploitation results in arbitrary code execution in the context of the FTM application, with full compromise of confidentiality, integrity, and availability of the system — a critical concern given FTM’s role in processing financial transactions.

Affected software

  • IBM Financial Transaction Manager (FTM) for RedHat OpenShift versions 4.0.6.0 through 4.0.10.0 (including intermediate releases and Interim Fixes up through Interim Fix 064)

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade IBM Financial Transaction Manager (FTM) for RedHat OpenShift to version 4.0.11.0 or later, which resolves the code injection flaw.
  • If immediate patching is not possible: Restrict network access to FTM management and application interfaces to trusted internal networks only, and monitor for anomalous requests targeting FTM endpoints until the patch can be applied. Organizations should prioritize this upgrade given the critical severity and unauthenticated, network-exploitable nature of the flaw.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge