CVE-2026-18154

Analyzed Analyzed - Analysis Complete

Hard-Coded Cryptographic Key in IBM FTM for RedHat OpenShift

Publication date: 2026-09-22

Last updated on: 2026-10-08

Assigner: IBM Corporation

Description

IBM Financial Transaction Manager (FTM) for RedHat OpenShift could allow a remote attacker to obtain sensitive information due to the use of a hard-coded or predictable cryptographic key.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-09-22

Last Modified

2026-10-08

Generated

2026-10-13

AI Q&A

2026-09-23

EPSS Evaluated

2026-10-12

NVD

CVE-2026-18154

EUVD

EUVD-2026-84944

Affected Vendors & Products

Vendor	Product	Version / Range
ibm	financial_transaction_manager	From 4.0.7.0 (inc) to 4.0.11.0 (exc)
ibm	financial_transaction_manager	4.0.6.0
ibm	financial_transaction_manager	4.0.6.0
ibm	financial_transaction_manager	4.0.6.0
ibm	financial_transaction_manager	4.0.6.0
ibm	financial_transaction_manager	4.0.6.0
ibm	financial_transaction_manager	4.0.6.0
ibm	financial_transaction_manager	4.0.6.0

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-321	The product uses a hard-coded, unchangeable cryptographic key.

Attack-Flow Graph

Executive Summary

IBM Financial Transaction Manager (FTM) for RedHat OpenShift uses a hard-coded or predictable cryptographic key, allowing a remote attacker to obtain sensitive information by exploiting this weakness.

Detection Guidance

Detection of CVE-2026-18154 requires checking for hard-coded or predictable cryptographic keys in IBM Financial Transaction Manager (FTM) for RedHat OpenShift. Inspect configuration files and application logs for default or weak keys. Use tools like grep to search for known key patterns in FTM directories. Monitor network traffic for unusual cryptographic handshakes or data exposure.

Impact Analysis

An attacker could intercept or decrypt sensitive financial data transmitted or stored by the system due to the weak cryptographic key, leading to data breaches or unauthorized access.

Compliance Impact

This vulnerability could violate GDPR by exposing personal data or HIPAA by compromising protected health information, leading to legal penalties and loss of trust.

Mitigation Strategies

Replace any hard-coded or predictable cryptographic keys with strong, randomly generated keys. Review and update IBM FTM configurations to ensure secure key management practices are followed.

Hi! I’m here to help you understand CVE-2026-18154. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70