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

New CVE Detected

CVE-2026-18163 – Remote Code Execution via Insecure Deserialization – IBM Financial Transaction Mana

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

Summary

CVE-2026-18163 is a critical deserialization-of-untrusted-data vulnerability (CWE-502) in IBM Financial Transaction Manager (FTM) for RedHat OpenShift. A remote, unauthenticated attacker can supply crafted serialized data to the application and achieve arbitrary code execution on the underlying server. IBM rates the flaw at CVSS v3.1 9.8 (Critical), and it was disclosed as part of an IBM security bulletin covering multiple FTM vulnerabilities published in September 2026.

Technical details

  • Root cause: FTM for RedHat OpenShift improperly deserializes untrusted input without adequate type or integrity validation, allowing attacker-controlled object streams to be reconstructed and executed by the application.
  • Trigger conditions: An attacker sends a specially crafted serialized payload to a reachable FTM service endpoint; no authentication or user interaction is required to trigger the flaw.
  • Attack vector: Network — the vulnerable component is exposed over the network, making the flaw remotely exploitable without local access or privileges.
  • Impact: Successful exploitation results in arbitrary code execution in the context of the FTM application, giving an attacker full compromise of confidentiality, integrity, and availability of the payment-processing platform and the data it handles.

Affected software

  • IBM Financial Transaction Manager (FTM) for RedHat OpenShift, versions 4.0.6.0 through 4.0.10.0 (including 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 IBM confirms resolves this vulnerability.
  • If patching cannot occur immediately: Restrict network access to FTM management and service endpoints to trusted internal networks only, and monitor for anomalous or malformed serialized-object traffic reaching the application, since IBM has not published an alternative workaround for this issue.

References

Are you exposed?

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

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

Subscribe to Threat Center RSS

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

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge