Targets IBM Financial Transaction Manager used in payment operations; stored XSS enables operator session hijack and unauthorized payment actions — high-impact for banks/payment providers.
CVE-2026-18872
Stored XSS in IBM FTM UI can hijack operator sessions and enable unauthorized payments
Is CVE-2026-18872 being exploited?
Not confirmed. CVE-2026-18872 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.
How severe is CVE-2026-18872?
CVE-2026-18872 is rated Critical with a CVSS score of 9.3. 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-18872?
Not known from our data. No patch reference has been recorded for CVE-2026-18872, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-18872 affect?
CVE-2026-18872 affects IBM Financial Transaction Manager (FTM) for RedHat OpenShift, FTM UI NetworkAcknowledgement React component, OpenShift deployments running IBM FTM. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-18872?
Restrict admin UI access, apply input validation/encoding, rotate operator sessions, deploy vendor patch when released
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Stored XSS lets attackers execute scripts in operator browsers to hijack sessions and initiate/alter payments as authenticated operators.
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.