FTM processes financial transactions; an auth bypass in widely deployed IBM finance software can expose transaction data and enable fraud across financial institutions.
CVE-2026-18181
Auth bypass via hard-coded crypto key in IBM FTM on OpenShift
Is CVE-2026-18181 being exploited?
Not confirmed. CVE-2026-18181 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.39% probability of exploitation in the next 30 days.
How severe is CVE-2026-18181?
CVE-2026-18181 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-18181?
Yes. A fix has been recorded for CVE-2026-18181. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-18181 affect?
CVE-2026-18181 affects IBM Financial Transaction Manager (FTM) for RedHat OpenShift. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-18181?
Follow IBM advisory, apply patch/mitigation, rotate keys, restrict FTM access
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote authentication bypass via hard-coded cryptographic key allows unauthorized access to transaction data and potential fraudulent actions.
Immediate action required
- affected>= 4.0.6.0 and <= 4.0.10.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- none
- automatable
- no
- technical impact
- total
Assessed by CISA 23 Sept 2026 (SSVC 2.0.3).
timeline
- 23 Sept 2026Published
- 23 Sept 2026CISA SSVC assessment: exploitation none · same day later
- 23 Sept 2026CVE record last updated · same day later
- 24 Sept 2026Analysed by vulneraibility.com · same day later
- Patchibm.com /support/pages/node/7288641
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.