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
- 7.5 High severity
watsonx.data: Improper Restriction of Communication Channel to Intended Endpoints
IBM watsonx.data 2.2 through 2.3 IBM Lakehouse does not properly restrict communication between pods which could allow an attacker to transfer data between pods without restrictions.
- 7.5 High severity
Langflow Desktop: Authorization Bypass Through User-Controlled Key
IBM Langflow Desktop 1.0.0 through 1.8.4 Langflow could allow an unauthenticated user to view other users' images due to an indirect object reference through a user-controlled key.
- 7.5 High severity
Red Hat Hardened Images: Access of Resource Using Incompatible Type
A flaw was found in libxml2. This vulnerability occurs when the library processes a specially crafted XML Schema Definition (XSD) validated document that includes an internal entity reference. An attacker could exploit this by providing a malicious document, l
- 9.8 Critical severity
Total Storage Service Console (TSSC) / TS4500…: Improper Neutralization of Special Elements used in an OS Command
IBM Total Storage Service Console (TSSC) / TS4500 IMC 9.2, 9.3, 9.4, 9.5, 9.6 TSSC/IMC could allow an unauthenticated user to execute arbitrary commands with normal user privileges on the system due to improper validation of user supplied input.
- 7.2 High severity
Security Verify Directory (Container): Unrestricted Upload of File with Dangerous Type
IBM Security Verify Directory (Container) 10.0.0 through 10.0.0.3 IBM Security Verify Directory could be vulnerable to malicious file upload by not validating file type. A privileged user could upload malicious files into the system that can be sent to victims
- 8.8 High severity
Langflow Desktop: Deserialization of Untrusted Data
IBM Langflow Desktop 1.6.0 through 1.8.2 Langflow could allow an authenticated user to execute arbitrary code on the system, caused by an insecure default setting which permits the deserialization of untrusted data in the FAISS component.
- 7.8 High severity
Verify Identity Access Container: Execution with Unnecessary Privileges
IBM Verify Identity Access Container 11.0 through 11.0.2 and IBM Security Verify Access Container 10.0 through 10.0.9.1 and IBM Verify Identity Access 11.0 through 11.0.2 and IBM Security Verify Access 10.0 through 10.0.9.1 could allow a locally authenticated
- 7.2 High severity
Verify Identity Access Container: Server-Side Request Forgery
IBM Verify Identity Access Container 11.0 through 11.0.2 and IBM Security Verify Access Container 10.0 through 10.0.9.1 and IBM Verify Identity Access 11.0 through 11.0.2 and IBM Security Verify Access 10.0 through 10.0.9.1 allows an attacker to contact intern
- 7.9 High severity
Verify Identity Access Container: Inclusion of Functionality from Untrusted Control Sphere
IBM Verify Identity Access Container 11.0 through 11.0.2 and IBM Security Verify Access Container 10.0 through 10.0.9.1 and IBM Verify Identity Access 11.0 through 11.0.2 and IBM Security Verify Access 10.0 through 10.0.9.1 could allow a locally authenticated
- 8.8 High severity
DataPower Gateway 10.6CD: Cross-Site Request Forgery
IBM DataPower Gateway 10.6CD 10.6.1.0 through 10.6.5.0 and IBM DataPower Gateway 10.5.0 10.5.0.0 through 10.5.0.20 and IBM DataPower Gateway 10.6.0 10.6.0.0 through 10.6.0.8 IBM DataPower Gateway is vulnerable to cross-site request forgery which could allow an
- 9.8 Critical severity
Verify Identity Access Container: Improper Authentication
IBM Verify Identity Access Container 11.0 through 11.0.2 and IBM Security Verify Access Container 10.0 through 10.0.9.1 and IBM Verify Identity Access 11.0 through 11.0.2 and IBM Security Verify Access 10.0 through 10.0.9.1 under certain load conditions could
- 7.3 High severity
Verify Identity Access Container: Improper Neutralization of Special Elements used in an OS Command
IBM Verify Identity Access Container 11.0 through 11.0.2 and IBM Security Verify Access Container 10.0 through 10.0.9.1 and IBM Verify Identity Access 11.0 through 11.0.2 and IBM Security Verify Access 10.0 through 10.0.9.1 could allow an unauthenticated user
- 7.5 High severity
Aspera Shares: Use of a Broken or Risky Cryptographic Algorithm
IBM Aspera Shares 1.9.9 through 1.11.0 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information
- 8.8 High severity
Storage Protect Server: Improper Neutralization of Special Elements used in an SQL Command
IBM Storage Protect Server 8.2.0 IBM Storage Protect Plus Server is vulnerable to SQL injection. A remote attacker could send specially crafted SQL statements, which could allow the attacker to view, add, modify, or delete information in the back-end database.
- 7.5 High severity
Concert: Use of a Cryptographic Primitive with a Risky Implementation
IBM Concert 1.0.0 through 2.2.0 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information
- 9.8 Critical severity
WebSphere Application Server - Liberty: Use of Default Password
IBM WebSphere Application Server - Liberty 17.0.0.3 through 26.0.0.3 IBM WebSphere Application Server Liberty could provide weaker than expected security when administering security settings.
- 7.2 High severity
WebSphere Application Server - Liberty: Exposure of Sensitive Information to an Unauthorized Actor
IBM WebSphere Application Server - Liberty 17.0.0.3 through 26.0.0.3 IBM WebSphere Application Server Liberty is affected by privilege escalation. A privileged user could gain additional access to the application server.
- 9.1 Critical severity
Db2 Recovery Expert: Missing Support for Integrity Check
IBM Db2 Recovery Expert for Linux, UNIX and Windows 5.5 IF 2 could allow an attacker to modify or corrupt data due to an insecure mechanism used for verifying the integrity of the data during transmission.
- 7.5 High severity
Sterling B2B Integrator: Improper Neutralization of Special Elements used in a Command
IBM Sterling B2B Integrator and and IBM Sterling File Gateway 6.1.0.0 through 6.1.2.7_2, 6.2.0.0 through 6.2.0.5_1, 6.2.1.0 through 6.2.1.1_1, and 6.2.2.0 could allow an unauthenticated attacker to send a specially crafted request that causes the application t
- 7.2 High severity
Sterling B2B Integrator: Improper Neutralization of Special Elements used in an SQL Command
IBM Sterling B2B Integrator and IBM Sterling File Gateway 6.1.0.0 through 6.1.2.7_2, 6.2.0.0 through 6.2.0.5_1, and 6.2.1.0 through 6.2.1.1_1 are vulnerable to SQL injection. An administrative user could send specially crafted SQL statements, which could allow
- 7.5 High severity
Sterling Partner Engagement Manager: Generation of Error Message Containing Sensitive Information
IBM Sterling Partner Engagement Manager 6.2.3.0 through 6.2.3.5 and 6.2.4.0 through 6.2.4.2 could allow a remote attacker to obtain sensitive information when detailed technical error messages are returned. This information could be used in further attacks aga
- 7.5 High severity
Sterling Partner Engagement Manager: Use of a Key Past its Expiration Date
IBM Sterling Partner Engagement Manager 6.2.3.0 through 6.2.3.5 and 6.2.4.0 through 6.2.4.2 could allow an attacker to obtain sensitive user information using an expired access token
- 7.5 High severity
Sterling Partner Engagement Manager: Cleartext Transmission of Sensitive Information
IBM Sterling Partner Engagement Manager 6.2.3.0 through 6.2.3.5 and 6.2.4.0 through 6.2.4.2 could allow a remote attacker to obtain sensitive information in cleartext in a communication channel that can be sniffed by unauthorized actors.
- 7.8 High severity
Trusteer Rapport installer: Uncontrolled Search Path Element
IBM Trusteer Rapport installer 3.5.2309.290 IBM Trusteer Rapport could allow a local attacker to execute arbitrary code on the system, caused by DLL uncontrolled search path element vulnerability. By placing a specially crafted file in a compromised folder, an
- 7.5 High severity
Aspera Orchestrator: Use of HTTP Request With Sensitive Query String
IBM Aspera Orchestrator 3.0.0 through 4.1.2 stores sensitive information in URL parameters. This may lead to information disclosure if unauthorized parties have access to the URLs via server logs, referrer header or browser history.
- 7.5 High severity
InfoSphere Information Server: Improper Restriction of XML External Entity Reference
IBM InfoSphere Information Server 11.7.0.0 through 11.7.1.6 An XML External Entity (XXE) vulnerability in IBM InfoSphere Information Server could allow attackers to retrieve sensitive information from the server.
- 7.5 High severity
Aspera faspio Gateway: Use of a Broken or Risky Cryptographic Algorithm
IBM Aspera faspio Gateway 1.3.6 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information
- 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.1.2 through 5.3.0 could allow an authenticated user to execute arbitrary commands with normal user privileges on the system due to improper validation of user supplied input through the wrapped command component.
- 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.1.2 through 5.3.0 could allow an authenticated user to execute arbitrary commands with normal user privileges on the system due to improper validation of user supplied input through the user-defined function component.
- 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.1.2 through 5.3.0 could allow an authenticated user to execute arbitrary commands with normal user privileges on the system due to improper validation of user supplied input through the job subroutine component.
- 9.8 Critical severity
WebSphere Application Server - Liberty: Use of Hard-coded Credentials
IBM WebSphere Application Server - Liberty 17.0.0.3 through 26.0.0.2 IBM WebSphere Application Server Liberty could provide weaker than expected security when using the Security Utility when administering security settings.
- 7.8 High severity
Storage Scale: Incorrect Permission Assignment for Critical Resource
IBM Storage Scale IBM S through rage Scale 5.2.3.0 - 5.2.3.5, and IBM S through rage Scale 6.0.0.0 - 6.0.0.1 could allow a local user to unintentionally trigger additional permissions for resources in a way that allows that resource to be executed by unintende
- 7.5 High severity
DataStage on Cloud Pak for Data: Exposure of Sensitive System Information to an Unauthorized Control Sphere
IBM DataStage on Cloud Pak for Data 5.1.2 through 5.3.0 returns sensitive information in an HTTP response that could be used in further attacks against the system.
- 8.8 High severity
DataStage on Cloud Pak: Unrestricted Upload of File with Dangerous Type
IBM DataStage on Cloud Pak for Data could allow an authenticated user to execute arbitrary commands and gain access to sensitive information due to unrestricted file uploads.
- 7.4 High severity
Concert: Incorrect Permission Assignment for Critical Resource
IBM Concert 1.0.0 through 2.1.0 could allow a local user with specific knowledge about the system's architecture to escalate their privileges due to incorrect file permissions for critical resources.
- 7.5 High severity
Security QRadar EDR: Inadequate Encryption Strength
IBM Security QRadar EDR 3.12 through 3.12.23 IBM Security ReaQta uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.
- 8.8 High severity
IBM Security QRadar EDR 3.12 through 3.12.23 does not invalidate session after a session…
IBM Security QRadar EDR 3.12 through 3.12.23 does not invalidate session after a session expiration which could allow an authenticated user to impersonate another user on the system.
- 8.8 High severity
IBM Security QRadar EDR 3.12 through 3.12.23 does not invalidate session after a session…
IBM Security QRadar EDR 3.12 through 3.12.23 does not invalidate session after a session expiration which could allow an authenticated user to impersonate another user on the system.
- 9.8 Critical severity
Concert: Use of Hard-coded Credentials
IBM Concert 1.0.0 through 2.1.0 could allow a remote attacker to obtain sensitive information or perform unauthorized actions due to the use of hard coded user credentials.
- 7.5 High severity
DB2 Merge Backup for Linux, UNIX and Windows: Sensitive Information in Resource Not Removed Before Reuse
IBM DB2 Merge Backup for Linux, UNIX and Windows 12.1.0.0 could allow an attacker to access sensitive information in memory due to the buffer not properly clearing resources.