Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate to FTM with low-privilege account
-
DeliveryCraft request with spoofed HTTP header
-
ExploitSubmit transaction with falsified header
-
ExecutionFTM writes forged audit-log entry
-
ImpactRepudiate or conceal transaction activity
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A09:2025 - Security Logging & Alerting Failures
ASVS 5.0
V16 - Security Logging and Error Handling Sufficient logging implementation
|
| Exploitation Conditions | Requires an authenticated session to IBM Financial Transaction Manager (FTM) for RedHat OpenShift (PR:L) and the ability to send requests containing a client-supplied HTTP header that FTM improperly validates; the attacker uses this header to write falsified entries into the transaction audit log. Limiting factors: valid low-privilege credentials are mandatory (no unauthenticated path), impact is confined to audit-log integrity (I:L) with no data exposure or service disruption, and the product is a specialized financial-transaction platform with a small deployment base. No user interaction is required (UI:N). |
| Impact | This is a genuinely low-priority issue, and the signals are consistent rather than conflicting. The vendor/NVD CVSS of 4.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N) captures a narrow integrity-only defect: a remote but authenticated (PR:L) attacker can falsify transaction audit logs by manipulating a client-supplied HTTP header (CWE-778, insufficient/improper logging). There is no confidentiality (C:N) or availability (A:N) impact, and integrity impact is limited (I:L) because the flaw corrupts audit/accountability records rather than the transactions themselves. No EPSS score, no CISA KEV listing, and no public exploit code are present in the input - no public exploit identified at time of analysis. No SSVC decision data is provided. The realistic threat is an insider or a compromised low-privilege account repudiating actions or hiding fraudulent transaction activity from auditors, not mass or automated exploitation. Priority should be routine patching, not emergency response. |
| Exploit ScenarioDerived | An authenticated FTM user (or attacker with stolen low-privilege credentials) submits transaction requests with a crafted/spoofed HTTP header that FTM fails to validate, causing forged or misleading entries to be written to the transaction audit log. This lets the attacker obscure their true actions or attribute activity to another source, undermining forensic accountability. No public exploit code is identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 22, 2026
Authenticated remote users of IBM Financial Transaction Manager (FTM) for Red Hat OpenShift can forge entries in the transaction audit log by supplying a crafted HTTP header that the application fails to validate properly. Successful abuse requires only valid low-privilege credentials (CVSS 3.1 base 4.3, AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N), so the practical consequence is limited to the integrity of the audit trail - no data disclosure, no service disruption, and no unauthenticated attack path. There is no public exploit identified at time of analysis, no CISA KEV listing, and no EPSS score provided; combined with the narrow, specialized deployment footprint of the platform, this is a genuinely low-priority issue whose signals are consistent rather than conflicting.
RemediationAI
No vendor-released patch identified at time of analysis - the provided reference set contains only the IBM advisory page, with no fix version, PR, or commit cited, so the first step is to consult https://www.ibm.com/support/pages/node/7288641 directly for the current remediation statement and any available fix level for FTM for Red Hat OpenShift. Until a fix is applied, the most effective compensating control is to stop untrusted client headers from reaching the audit-logging path: terminate HTTP at the OpenShift ingress/router or an external reverse proxy and strip or normalize any headers not on an explicit allowlist before forwarding to FTM, with the trade-off that over-aggressive header stripping can break integrations or authentication flows that legitimately depend on forwarded headers, so the allowlist must be tested in a staging environment first. Because the vector requires a valid low-privilege session, tightly review and reduce FTM accounts to the minimum needed and rotate credentials for any operator role that does not require transaction submission, accepting the operational overhead of narrower role assignments. Complement this with independent, out-of-band verification of the audit trail - for example shipping FTM logs to a write-once or separately administered SIEM/log store that applies its own server-side source labelling rather than trusting application-supplied fields - which lets you detect falsified entries but does not prevent the initial write. Finally, restrict network reachability to the FTM transaction endpoints to trusted service networks and monitor for anomalous header patterns in the request stream, understanding that these are detective rather than preventative measures and do not substitute for a vendor fix.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause class is CWE-778 (Insufficient Logging), realized here as insufficient validation of a client-supplied HTTP header that FTM for Red Hat OpenShift apparently incorporates into its transaction audit records. Audit logging is a trust-boundary problem: any value an application copies from an untrusted request into a log record must be treated as attacker-controlled input, because unvalidated header content lets a caller influence - or in this case falsify - the recorded facts of a transaction. FTM is a financial-messaging and transaction platform typically deployed on OpenShift/Kubernetes, so its audit log is the primary evidentiary artifact for transaction reconciliation, dispute resolution, and regulatory review; corruption of that record undermines downstream forensic and compliance workflows even though the CVSS impact is confined to I:L. The advisory is issued by IBM PSIRT and cross-tagged to Red Hat because of the OpenShift delivery model. No CPE entries were supplied, so the exact affected release train and fix level could not be confirmed from the available data; only a single vendor support reference (https://www.ibm.com/support/pages/node/7288641) was provided, and no EPSS, KEV, or CWE-beyond-778 enrichment accompanied it.
Know when Financial Transaction Manager gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Remote authenticated user (PR:L) manipulates an unvalidated header to corrupt audit logs; integrity-only limited impact (I:L), no confidentiality or availability effect.
Primary rating from Vendor (us).
CVSS VectorVendor: us
DescriptionCVE.org
IBM Financial Transaction Manager (FTM) for RedHat OpenShift could allow a remote authenticated attacker to falsify transaction audit logs due to improper validation of a client-supplied HTTP header.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
IBM Financial Transaction Manager for Digital Payments for Multi-Platform 3.1.0 is vulnerable to SQL injection. Rated cr
IBM Financial Transaction Manager for SWIFT Services 3.2.4 is vulnerable to an XML External Entity Injection (XXE) attac
IBM Financial Transaction Manager (FTM) for Multi-Platform (MP) 3.0.0.0 through 3.0.0.7 is vulnerable to SQL injection.
IBM Financial Transaction Manager for Digital Payments for Multi-Platform 3.0.2, 3.0.4, 3.0.6, and 3.2.0 is vulnerable t
Remote code execution via ESQL command injection affects IBM Financial Transaction Manager (FTM) for Red Hat OpenShift,
Sensitive information disclosure in IBM Financial Transaction Manager (FTM) for Red Hat OpenShift stems from the product
Cleartext transmission of sensitive information in IBM Financial Transaction Manager (FTM) for Red Hat OpenShift exposes
Message forgery in IBM Financial Transaction Manager (FTM) for Red Hat OpenShift lets remote, unauthenticated attackers
In the Message Entry and Repair (MER) facility of IBM Financial Transaction Manager for SWIFT Services 3.2.4 the sending
Hard-coded cryptographic keys and initialization vectors in IBM Financial Transaction Manager (FTM) for Red Hat OpenShif
Cross-site request forgery (CSRF) vulnerability in the OAC component in IBM Financial Transaction Manager (FTM) 2.0 befo
IBM Financial Transaction Manager for ACH Services for Multi-Platform 3.0.2 could allow an authenticated user to obtain
EUVD-2026-84942
GHSA-f7vq-hm4q-h5hr
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB