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. EPSS currently estimates a 0.31% probability of exploitation in the next 30 days.
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?
Yes. A fix has been recorded for CVE-2026-18872. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
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.
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
- 26 Sept 2026Analysed by vulneraibility.com · 2 days 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.