CVE-2026-18177
IBM Financial Transaction Manager (FTM) is Impacted by Multiple Vulnerabilities
No known exploitation. EPSS puts it in the 7th percentile. Fixed in 4.0.11.0.
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.10.0Upgrade to: after 4.0.10.0Stated 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
Steps
Written by AI from the record- Confirm you are running Financial Transaction Manager (FTM) for RedHat OpenShift and check its current version.
- Restrict network access to the FTM environment so only trusted systems can reach it, as a stop-gap.
- Update FTM to version 4.0.11.0, the fixed release from IBM.
- After updating, verify that transaction-initiation endpoints now require proper authorization before processing.
What it is
From the CVE record
IBM Financial Transaction Manager (FTM) for RedHat OpenShift could allow a remote attacker to execute unauthorized payment actions due to missing authorization checks.
In plain language
Written by AI from the recordA bug in IBM's Financial Transaction Manager for Red Hat OpenShift lets someone on the same network push or alter money transfers without logging in, so if you run this system you should update it to version 4.0.11.0 right away.
CWE-862 missing authorization check in IBM Financial Transaction Manager (FTM) for RedHat OpenShift allows an unauthenticated attacker with adjacent network access to initiate or modify payment transactions without any permission verification.
If you're affected
- Unauthorized fund transfers
- Financial transaction tampering
- Regulatory/compliance exposure
- Loss of customer trust
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- 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 7th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
9 events over 14 days, from the signal feeds we watch.
- Patch availablerecord updated
- Patch availablepatch available, published, weakness classified, att&ck mapped, record updated, record updated
Affected products
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
Scored 7.1 by NVD.
How it is reached
- Attack Vector AdjacentRequires access to the local network (e.g. same Wi-Fi, Bluetooth)
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- 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 NoneNo confidentiality impact
- Integrity HighTotal loss of integrity — attacker can modify any data in the component
- Availability LowReduced performance or intermittent disruption of service
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
Sources
References in the record
In the news
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.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI