IBM vulnerabilities
We track 1,482 vulnerabilities in IBM products across 60+ products. 1,480 are rated high or critical, and 12 have been exploited in real attacks. The most recent was published on November 13, 2026.
Latest IBM vulnerabilities
- 8.8 High severity
Guardium Data Protection: Improper Limitation of a Pathname to a Restricted Directory
IBM Guardium Data Protection 12.2 could allow a remote attacker to obtain sensitive information, delete arbitrary files, or execute arbitrary code due to improper limitation of a pathname to a restricted directory.
- 8.8 High severity
Guardium Data Protection: Plaintext Storage of a Password
IBM Guardium Data Protection 12.2 stores internal REST service-account passwords in a reversible plaintext-equivalent format. An authenticated attacker who gains access to the stored credential could recover the password and obtain an administrative REST acces
- 7.1 High severity
DataStage on Cloud Pak for Data: Improper Limitation of a Pathname to a Restricted Directory
IBM DataStage on Cloud Pak for Data 5.4.0.0 could allow a remote authenticated attacker to traverse directories on the system due to improper limitation of a pathname to a restricted directory.
- 8.8 High severity
DataStage on Cloud Pak for Data: Deserialization of Untrusted Data
IBM DataStage on Cloud Pak for Data 5.4.0.0 could allow a remote authenticated attacker to execute arbitrary code due to unsafe deserialization of untrusted data.
- 8.8 High severity
DataStage on Cloud Pak for Data: Improper Neutralization of Special Elements used in an OS Command
IBM DataStage on Cloud Pak for Data 5.4.0.0 could allow a remote authenticated attacker to execute arbitrary commands due to improper neutralization of environment variables.
- 7.7 High severity
DataStage on Cloud Pak for Data: Server-Side Request Forgery
IBM DataStage on Cloud Pak for Data 5.4.0.0 could allow a remote authenticated attacker to obtain sensitive information due to improper validation of the X-Forwarded-Proto header.
- 8.8 High severity
DataStage on Cloud Pak for Data: Improper Neutralization of Special Elements used in an OS Command
IBM DataStage on Cloud Pak for Data 5.4.0.0 could allow a remote authenticated attacker to execute arbitrary commands due to improper neutralization of special elements used in an OS command.
- 8.8 High severity
DataStage on Cloud Pak for Data: Improper Neutralization of Special Elements used in an OS Command
IBM DataStage on Cloud Pak for Data 5.4.0.0 could allow a remote authenticated attacker to execute arbitrary commands due to improper neutralization of special elements used in an OS command.
- 8.8 High severity
DataStage on Cloud Pak for Data: Improper Neutralization of Special Elements used in an OS Command
IBM DataStage on Cloud Pak for Data 5.4.0.0 could allow a remote authenticated attacker to execute arbitrary code due to improper neutralization of special elements used in an OS command.
- 8.6 High severity
Enterprise Build of Quarkus: Improper Neutralization of Special Elements used in an SQL Command
IBM Enterprise Build of Quarkus 3.27.1 through 3.27.5.SP1, and 3.33.1 through 3.33.3.SP1 is vulnerable to SQL injection. A remote unauthenticated attacker could send specially crafted SQL statements, which could allow the attacker to view, add, modify, or dele
- 7.7 High severity
DataStage on Cloud Pak for Data: Improper Restriction of XML External Entity Reference
IBM DataStage on Cloud Pak for Data 5.4.0.0 could allow a remote authenticated attacker to obtain sensitive information due to an XML external entity (XXE) injection.
- 7.7 High severity
DataStage on Cloud Pak for Data: Insufficiently Protected Credentials
IBM DataStage on Cloud Pak for Data 5.4.0.0 could allow an authenticated user to access sensitive information due to improper handling of encrypted credentials. An attacker could exploit this vulnerability to obtain credentials intended for other users or envi
- 8.8 High severity
DataStage on Cloud Pak for Data: Improper Neutralization of Special Elements used in an OS Command
IBM DataStage on Cloud Pak for Data 5.4.0.0 could allow a remote authenticated attacker to execute arbitrary commands due to improper neutralization of special elements used in an OS command.
- 8.8 High severity
DataStage on Cloud Pak for Data: Improper Neutralization of Special Elements used in an OS Command
IBM DataStage on Cloud Pak for Data 5.4.0.0 could allow a remote authenticated attacker to execute arbitrary code due to improper escaping of connector property values during OSH script generation.
- 8.8 High severity
DataStage on Cloud Pak for Data: Improper Neutralization of Special Elements used in an OS Command
IBM DataStage on Cloud Pak for Data 5.4.0.0 could allow a remote authenticated attacker to execute arbitrary commands due to improper neutralization of special elements used in an OS command.
- 7.8 High severity
Concert: Uncontrolled Search Path Element
IBM Concert 1.0.0 through 3.0.0 invokes operating system commands without fully qualifying executable paths or adequately restricting search path resolution. As a result, an attacker with local system access can manipulate the search path environment to execut
- 9.8 Critical severity
Concert: Use After Free
IBM Concert 1.0.0 through 3.0.0 references or accesses memory after it has been freed. This allows an attacker who can influence program execution or input may exploit this condition to corrupt memory, cause application crashes, or execute arbitrary code.
- 7.8 High severity
Concert: Double Free
IBM Concert 1.0.0 through 3.0.0 has a double free vulnerability that exists due to incorrect memory management. A local attacker can exploit this flaw to corrupt heap memory and execute arbitrary code in the context of the affected process.
- 7.8 High severity
Concert: Buffer Copy without Checking Size of Input
IBM Concert 1.0.0 through 3.0.0 is vulnerable to a buffer overflow, caused by improper bounds checking. A local user could overflow the buffer and execute arbitrary code on the system.
- 9.8 Critical severity
Concert: Improper Neutralization of Special Elements used in an OS Command
IBM Concert 1.0.0 through 3.0.0 allows an unauthenticated remote attacker can supply specially crafted input that is incorporated into OS commands, resulting in arbitrary command execution on the underlying system. Successful exploitation allows remote code ex
- 8.2 High severity
Financial Transaction Manager (FTM) for RedHat…: Improper Neutralization of Special Elements in Output Used by a Downstream Component
IBM Financial Transaction Manager (FTM) for RedHat OpenShift could allow a remote attacker to manipulate database queries due to improper neutralization of special elements in a boolean expression.
- 7.3 High severity
Financial Transaction Manager (FTM) for RedHat…: Improper Neutralization of Special Elements in Output Used by a Downstream Component
IBM Financial Transaction Manager (FTM) for RedHat OpenShift is vulnerable to RAG poisoning via unauthenticated runbook upsert (CWE-74) in the FTM AI agent server (api.vectordb.runbooks.js:51). An unauthenticated attacker can insert malicious runbook content i
- 9.3 Critical severity
Financial Transaction Manager (FTM) for RedHat…: Improper Neutralization of Input During Web Page Generation
IBM Financial Transaction Manager (FTM) for RedHat OpenShift is vulnerable to stored cross-site scripting (CWE-79) in the FTM UI NetworkAcknowledgement React component (NetworkAcknowledgement.jsx:42). A malicious actor can inject script into stored network ack
- 8.8 High severity
Financial Transaction Manager (FTM) for RedHat…: Deserialization of Untrusted Data
IBM Financial Transaction Manager (FTM) for RedHat OpenShift is vulnerable to unauthenticated remote code execution via Java native deserialization on the PayDir Business Rules Manager RMI SSL endpoint (BrmRMISSLServerSocketFactory.java:95, EP8). An adjacent-n
- 7.3 High severity
Financial Transaction Manager (FTM) for RedHat…: Missing Authentication for Critical Functionality
IBM Financial Transaction Manager (FTM) for RedHat OpenShift could allow a remote attacker to access sensitive information and modify system configurations due to missing authentication for a critical function.
- 7.4 High severity
Financial Transaction Manager (FTM) for RedHat…: Improper Restriction of XML External Entity Reference
IBM Financial Transaction Manager (FTM) for RedHat OpenShift could allow a remote attacker to obtain sensitive information due to an XML external entity (XXE) injection flaw.
- 8.1 High severity
Financial Transaction Manager (FTM) for RedHat…: Use of Hard-coded Cryptographic Key
IBM Financial Transaction Manager (FTM) for RedHat OpenShift could allow a remote attacker to bypass authentication and access sensitive information due to a hard-coded cryptographic key.
- 7.1 High severity
Financial Transaction Manager (FTM) for RedHat…: Missing Authorization
IBM Financial Transaction Manager (FTM) for RedHat OpenShift could allow a remote attacker to execute unauthorized payment actions due to missing authorization checks.
- 7.4 High severity
Financial Transaction Manager (FTM) for RedHat…: Cleartext Transmission of Sensitive Information
IBM Financial Transaction Manager (FTM) for RedHat OpenShift could allow a remote attacker to obtain sensitive information due to cleartext transmission of sensitive information.
- 7.4 High severity
Financial Transaction Manager (FTM) for RedHat…: Improper Restriction of XML External Entity Reference
IBM Financial Transaction Manager (FTM) for RedHat OpenShift could allow a remote attacker to obtain sensitive information due to improper restriction of XML external entity references.
- 9.9 Critical severity
Financial Transaction Manager (FTM) for RedHat…: Improper Limitation of a Pathname to a Restricted Directory
IBM Financial Transaction Manager (FTM) for RedHat OpenShift could allow a remote authenticated attacker to obtain sensitive information due to improper validation of symbolic links.
- 9.8 Critical severity
Financial Transaction Manager (FTM) for RedHat…: Deserialization of Untrusted Data
IBM Financial Transaction Manager (FTM) for RedHat OpenShift could allow a remote attacker to execute arbitrary code due to improper deserialization of untrusted data.
- 9.8 Critical severity
Financial Transaction Manager (FTM) for RedHat…: Improper Control of Generation of Code
IBM Financial Transaction Manager (FTM) for RedHat OpenShift could allow a remote attacker to execute arbitrary code due to improper neutralization of user-controlled input within the new Function constructor.
- 7.5 High severity
Financial Transaction Manager (FTM) for RedHat…: Use of Hard-coded Cryptographic Key
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.
- 7.1 High severity
Financial Transaction Manager (FTM) for RedHat…: Use of a Broken or Risky Cryptographic Algorithm
IBM Financial Transaction Manager (FTM) for RedHat OpenShift could allow a remote authenticated attacker to obtain sensitive information and forge authentication tags due to the use of hard-coded cryptographic keys and initialization vectors.
- 7.5 High severity
Financial Transaction Manager (FTM) for RedHat…: Improper Verification of Cryptographic Signature
IBM Financial Transaction Manager (FTM) for RedHat OpenShift could allow a remote attacker to forge validly-signed messages due to improper verification of cryptographic signatures.
- 8.1 High severity
Financial Transaction Manager (FTM) for RedHat…: Improper Neutralization of Special Elements used in an SQL Command
IBM Financial Transaction Manager (FTM) for RedHat OpenShift could allow a remote attacker to execute arbitrary ESQL commands due to improper neutralization of special elements used in an ESQL command.
- 7.5 High severity
Financial Transaction Manager (FTM) for RedHat…: Cleartext Transmission of Sensitive Information
IBM Financial Transaction Manager (FTM) for RedHat OpenShift could allow a remote attacker to obtain sensitive information due to cleartext transmission of sensitive information.
- 7.5 High severity
Financial Transaction Manager (FTM) for RedHat…: Use of Externally-Controlled Input to Select Classes or Code
IBM Financial Transaction Manager (FTM) for RedHat OpenShift could allow a remote attacker to cause a denial of service due to the improper use of reflection with externally controlled input.
- 7.5 High severity
Financial Transaction Manager (FTM) for RedHat…: Improper Limitation of a Pathname to a Restricted Directory
IBM Financial Transaction Manager (FTM) for RedHat OpenShift could allow a remote attacker to read arbitrary files due to improper path canonicalization.