CVE Tools
Track your stack

CVE-2026-18173

IBM Financial Transaction Manager (FTM) is Impacted by Multiple Vulnerabilities

No known exploitation. EPSS puts it in the 14th percentile. Fixed in 4.0.11.0.

CVSS 3.13.7LowEPSS percentile14th0.2% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix4.0.11.0Upgrade to this build

Published Updated Sources: CVE.org, NVD

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • IBM Financial Transaction Manager for RedHat OpenShiftAffected: ≥ 4.0.6.0, ≤ 4.0.6.0.0.6.0 Refresh (Operator…Upgrade to: after 4.0.6.0.0.6.0 Refresh (Operator…Stated by: CVE record
  • Ibm Financial Transaction ManagerAffected: ≥ 4.0.7.0, < 4.0.11.0Upgrade to: 4.0.11.0Stated by: NVD

Versions as the sources state them. Full version matrix after sign-in

What it is

From the CVE record

IBM Financial Transaction Manager (FTM) for RedHat OpenShift could allow a remote attacker to obtain sensitive information due to improper enforcement of mutual TLS authentication.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS14th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.2% chance of exploitation activity in the next 30 days, which ranks it in the 14th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

9 events over 15 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. Patch availablerecord updated
  3. Patch availablepublished, weakness classified, att&ck mapped, record updated

Affected products

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

Scored 3.7 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality LowSome restricted information is disclosed, but limited in scope
  • Integrity NoneNo integrity impact
  • Availability NoneNo availability impact

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

References in the record

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for IBM, not every advisory.