IBM
Monthly
Script injection in IBM Guardium Data Protection 12.2 allows a remote authenticated attacker with low-privileged web credentials to inject unsanitized input into web-generated pages, which then executes as JavaScript when another user views the affected page. The independent assessment treats this as a client-side cross-site scripting issue requiring victim interaction, with low confidentiality and integrity impact in the browser/session context and no availability impact, rather than host operating system code execution despite the vendor description's 'arbitrary code' phrasing. No public exploit was identified at time of analysis, and a vendor patch is available from IBM.
Authentication bypass in IBM Guardium Data Protection 12.2 lets an unauthenticated remote attacker evade the IP-based access controls guarding the Guardium management interface and reach that interface without satisfying the network allowlist. IBM rates the flaw 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), but our independent assessment scores it materially lower (C:L/I:N/A:N) because the bypass defeats the IP filter rather than the interface's own authentication, so real impact hinges on what the management interface permits once reached and whether it applies its own credentials. No public exploit code has been identified at time of analysis, and exploitation is only possible where the management interface is network-reachable and administrators treat IP allowlisting as the primary or sole control; deployments whose management plane is fully segmented behind a firewall with no attacker path are not exposed.
Path traversal in IBM Guardium Data Protection 12.2 lets a remote authenticated attacker with a low-privilege account manipulate file paths to reach locations outside the intended directory, producing a high integrity impact alongside limited confidentiality and availability effects. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L, base 7.6) confirms the flaw is network-reachable and low-complexity but gated behind a valid account, so exposure is bounded by the authentication requirement and the typically segmented management network these appliances sit on. No public exploit code has been identified at time of analysis and there is no CISA KEV listing; IBM has published a vendor patch, so remediation is available.
Local privilege escalation in IBM Guardium Data Protection 12.2 allows an attacker who already holds a low-privileged local account on the appliance - such as a constrained operator role, a compromised low-privileged process, or a malicious insider - to gain elevated privileges, with full compromise of confidentiality, integrity, and availability of the affected system. The flaw (CWE-269, improper privilege management) is rated CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), requiring no user interaction and no network-facing path; the local-access prerequisite makes it a post-compromise escalation step rather than a remote entry point. No public exploit code or confirmed active exploitation has been identified at time of analysis, and IBM has published a vendor patch advisory.
Unauthenticated OS command injection in IBM Guardium Data Protection 12.2 allows a remote attacker with network reachability to a vulnerable appliance component to execute arbitrary operating system commands, yielding full confidentiality, integrity, and availability impact on the affected system. The vendor CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, 8.1 High) confirms no authentication or user interaction is required, though the AC:H rating indicates exploitation depends on a precondition not fully specified by IBM rather than being reliably repeatable against any default install. No public exploit code or confirmed active exploitation was identified at time of analysis, but real-world risk is elevated because Guardium is a security-data platform that frequently holds sensitive audit and database activity records, and successful exploitation effectively equates to remote code execution on the appliance.
Authenticated OS command injection in IBM Guardium Data Protection 12.2 allows a remote attacker holding a valid low-privilege session to execute arbitrary operating-system commands on the affected appliance, with high impact to confidentiality, integrity, and availability (CVSS 3.1 base 8.8). The flaw is rated AV:N/AC:L/PR:L/UI:N/S:U, so exploitation requires credentials - authentication requirements are confirmed as authenticated (PR:L) by the assessed vector - but no user interaction and no non-default configuration; the specific vulnerable feature and input parameter are not disclosed in the advisory, and no public exploit code has been identified at time of analysis (not listed in CISA KEV). Realistic risk therefore centers on malicious insiders, compromised or reused operator accounts, and attackers who have already established a foothold on the management network, and IBM states a vendor patch is available.
Missing authorization checks in the REST API of IBM Guardium Data Protection 12.2 allow a remote, low-privileged authenticated attacker to perform actions beyond their assigned role and gain elevated privileges over the Guardium platform. Exploitation requires valid credentials for a low-privileged account (CVSS vector PR:L, AV:N, no user interaction), so this is not a pre-authentication flaw; reachability is further limited in most deployments because Guardium REST APIs normally sit on internal or management network segments. No public exploit code has been identified at time of analysis and the vulnerability is not listed as confirmed actively exploited (CISA KEV); the vendor has published a fix, and exploitability is constrained by the need for valid credentials and management-plane access.
Stored cross-site scripting in IBM Guardium Data Protection 12.2 lets an authenticated user of the web management console inject script that executes in a second user's browser when the affected page is rendered. The vendor scores this 9.6 (scope change, high confidentiality and integrity impact), but the independent assessment scores it CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N, treating the impact as confined to the victim's browser/session context rather than the underlying appliance operating system; the record's 'RCE' tag and the vendor's UI:N rating overstate what a CWE-79 input-neutralization flaw realistically delivers. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and IBM has published a patch advisory. This is a high-CVSS-but-lower-real-risk issue where the vendor scoring and tags overstate severity.
Unauthenticated insecure deserialization in the Change Audit System (CAS) listener of IBM Guardium Data Protection 12.2 allows a network attacker who can reach TCP port 16017 to submit crafted serialized messages that are insecurely deserialized and used for attacker-controlled reflective method dispatch, potentially resulting in unintended code execution on the Guardium appliance with high confidentiality, integrity, and availability impact. The vendor-reported base score is 9.8 (AV:N/AC:L/PR:N/UI:N); our independent assessment keeps the unauthenticated, no-user-interaction profile but applies AC:H, because the practical gating factor is whether an attacker has a network path to the non-standard CAS port rather than any product configuration toggle. No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited (not in CISA KEV); IBM has published a vendor patch advisory, and this should be treated as a genuinely high-priority issue for any deployment where port 16017 is reachable from untrusted networks, while remaining lower-risk in segmented or hardened environments where the listener is internal-only.
Command injection in IBM Guardium Data Protection 12.2 lets an authenticated, highly privileged administrator execute arbitrary shell commands with root privileges by supplying a crafted filename to the 'import remotelog_config file' CLI command. Successful exploitation compromises the confidentiality, integrity, and availability of the appliance, and no public exploit has been identified at time of analysis. IBM has released a fix via its support advisory, so exposure is limited to unpatched 12.2 deployments whose administrative CLI access is reachable by an attacker.
SQL injection in the Analytic Grid Service Handler of IBM Guardium Data Protection 12.2 allows a low-privileged authenticated user to reach the analytic cases grid endpoint and inject arbitrary SQL statements, giving unauthorized access to sensitive data and putting the confidentiality, integrity, and availability of the platform at high risk (CVSS 3.1 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Exploitation is constrained: it is not possible unauthenticated, since a valid web console account with at least low privilege is mandatory, and the attack surface is limited to the analytic cases grid feature rather than the whole product. No public exploit code has been identified at time of analysis, and IBM has published a vendor patch through support bulletin 7288040.
Command injection in the 'create csr wildcard' CLI command of IBM Guardium Data Protection 12.2 allows an authenticated privileged CLI user to embed shell metacharacters in the 'alias' input, breaking out of the restricted CLI and executing arbitrary commands with root privileges on the appliance. The CVSS v3.1 vector (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, 7.2 High) confirms this is not an unauthenticated remote compromise: the attacker must already hold privileged CLI credentials and CLI access, typically over SSH, making this fundamentally a restricted-shell-to-root privilege escalation rather than an external initial-access vector. Impact is total for confidentiality, integrity, and availability of the appliance given the root-level execution context; no public exploit code was identified at time of analysis, and CISA KEV does not list this CVE as actively exploited.
Unauthenticated remote code execution in IBM Guardium Data Protection 12.2 lets a network attacker who can reach the appliance interface that processes serialized input run arbitrary code in the context of the affected service, yielding full loss of confidentiality, integrity and availability (CVSS 9.8, AV:N/AC:L/PR:N/UI:N). The root cause is insecure deserialization of untrusted data (CWE-502), and because the assessed vector carries PR:N and UI:N, no credentials or user interaction are needed, so real-world exposure is determined almost entirely by network reachability to the Guardium management/collector segment rather than by the public internet. No public exploit code has been identified at time of analysis and the flaw is not listed in CISA KEV; IBM has published a vendor patch, which keeps this a top-tier remediation priority rather than an actively exploited emergency.
SQL injection in the New Query Builder REST Processor of IBM Guardium Data Protection 12.2 allows a low-privileged authenticated user to inject arbitrary SQL through the newQueryBuilder REST endpoint, enabling unauthorized read and modification of data held by the appliance and degrading system availability. The flaw carries a CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), reflecting remote reachability and high confidentiality, integrity and availability impact, but it is not pre-authentication: an attacker must already hold a valid low-privilege Guardium account and reach the appliance's REST interface. No public exploit code or confirmed active exploitation was identified at time of analysis, and IBM has published a vendor patch; because the entry point is standard Query Builder functionality rather than an optional component, the absence of an exploit is the only thing currently limiting real-world risk.
Unauthenticated SQL injection in the Load Balancer Groups component of IBM Guardium Data Protection 12.2 allows remote attackers to reach the Load Balancer Servlet endpoint and inject arbitrary SQL statements, potentially exposing managed data and degrading the confidentiality, integrity, and availability of the appliance (CVSS 8.6, with confidentiality impact rated high and integrity/availability impact limited). Per the CVSS vector PR:N/UI:N, no credentials or user interaction are required to attempt the attack, but practical risk depends on network exposure: Guardium appliances are normally deployed on internal management or security networks rather than the public internet, so reachability to the servlet is the principal gating condition. No public exploit code has been identified at time of analysis, and IBM has published remediation through its support advisory rather than confirmed in-the-wild activity.
IBM Guardium Data Protection 12.2 allows an authenticated low-privileged user to execute arbitrary operating system commands through an unspecified input validation flaw. The vulnerability, requiring a valid account but no user interaction and reachable over the network, executes commands with the low privileges of the compromised user, limiting direct system takeover but enabling data access or lateral movement. With EPSS at 0.26% and no public exploit or KEV listing, the immediate threat is limited, but the CVSS score of 8.8 and potential for abuse warrant prompt patching.
Authenticated OS command injection in IBM Guardium Data Protection 12.2 lets a user holding only low-privilege console credentials execute arbitrary operating-system commands on the affected appliance through the exportCertificate functionality, resulting in full loss of confidentiality, integrity, and availability (CVSS 3.1 base score 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Because the attack requires valid credentials and network reachability to the Guardium management interface, it is not usable by unauthenticated outsiders; CISA's SSVC assessment records Exploitation as 'none' and Automatable as 'no', and no public exploit code has been identified at time of analysis. EPSS is 0.63 percent (49th percentile), consistent with a targeted, credentialed issue rather than a broadly exploited one, and IBM has published a vendor patch.
Second-order SQL injection in IBM Guardium Data Protection 12.2 allows an unauthenticated remote attacker to submit SQL that is stored and later processed by the generateInsertQuery logic in change-tracker-data.sql, potentially compromising confidentiality, integrity, and availability. The supplied CVSS is 9.8 (AV:N/AC:L/PR:N/UI:N), but our independent assessment raises attack complexity to High because the second-order path requires both initial acceptance/storage of the payload and a subsequent internal operation that builds the INSERT query; this two-stage requirement is the main practical constraint. No public exploit identified at time of analysis or KEV-confirmed active exploitation is present in the supplied data, and IBM has published vendor patch information at its support advisory.
Authentication bypass in IBM Sterling File Gateway lets a remote, unauthenticated attacker forge or inject an unvalidated SSO header and obtain a fully authenticated session on the gateway's web interface. The flaw is rated CVSS 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N) because no credentials, privileges, or user interaction are required, and a successful bypass yields high confidentiality and integrity impact over file-transfer workflows. No public exploit identified at time of analysis, but exploitation is trivial for anyone who can reach an SSO-header-enabled deployment, so internet-exposed instances should be treated as high priority; IBM has published a fix advisory.
Unauthenticated SQL injection in IBM Platform RTM (the real-time monitoring component of Spectrum LSF) lets a remote attacker who can reach the product's web/reporting interface inject crafted SQL into a back-end database, reading, adding, modifying, or deleting data. The vendor rates it CVSS 3.1 8.6 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L), and our independent assessment agrees on severity while noting that in typical HPC/LSF deployments the component sits on a trusted cluster-management network rather than the public internet, which is the main real-world brake on exploitation; the assessed vector also raises the integrity impact to H (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L) because successful SQL injection against a writable application account commonly yields full row-level manipulation, not just partial. No public exploit code was identified at time of analysis and the flaw is not in CISA KEV, though the PR:N/UI:N profile means no credentials or user interaction are needed once the endpoint is reachable. Vendor patch availability is listed as available, giving administrators a direct fix path; the specific vulnerable parameter and page are not named in available data, so pre-auth reachability should be verified against the IBM advisory.
Heap-based buffer overflow in the IBM MQ C client shipped with IBM MQ for HPE NonStop 8.1.0 through 8.1.0.40 lets a remote attacker who controls the queue manager's responses crash the client process or potentially execute arbitrary code in its context (CVSS 3.1 base 8.1). The flaw is triggered when the client requests AMS (Advanced Message Security) policy data and the client fails to properly validate the returned queue manager response; exploitation is unauthenticated from the client side (PR:N) but requires the attacker to operate a malicious or compromised queue manager or to man-in-the-middle the client-to-queue-manager channel, which is why the vector carries AC:H. No public exploit code or confirmed active exploitation was identified at time of analysis, and a vendor patch is available.
Improper validation of message header offset values in IBM MQ for HPE NonStop 8.1.0 through 8.1.0.40 allows an authenticated MQ user with network reach to an affected queue manager to trigger an out-of-bounds read, which can leak queue manager memory (high confidentiality impact) and crash the broker (high availability impact), yielding a CVSS 3.1 score of 8.1. Exploitation requires valid credentials - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H - but no user interaction, and the requirement for authentication rules out anonymous abuse while the flaw is confined to the HPE NonStop platform port rather than all MQ deployments. No public exploit identified at time of analysis; a vendor patch is referenced in IBM's advisory.
An integer overflow in IBM MQ's MQINQ (inquire object attributes) request processing lets an authenticated remote user crash the queue manager and, per the vendor, potentially execute arbitrary code, giving the issue a CVSS 3.1 base score of 8.8 with high confidentiality, integrity and availability impact. Exploitation is network-based against the queue manager listener (default 1414/tcp), requires valid MQ credentials or connection authority (PR:L) and no user interaction; the vendor describes reliable code execution as a potential rather than confirmed outcome, so denial of service is the more assured impact. No public exploit identified at time of analysis, and a vendor fix is available per the IBM advisory.
IBM MQ for HPE NonStop versions 8.1.0 through 8.1.0.40 contain a heap-based buffer overflow (CWE-122) that is triggered during queue manager startup when improperly validated cluster migration data is processed. The flaw is exploitable only by an authenticated attacker who can supply crafted migration data to a queue manager participating in MQ clustering, and the dependable outcome is a denial of service (queue manager startup failure or crash), with arbitrary code execution considered only potentially achievable. Independent assessment rates the realistic impact lower than the vendor's 7.5 score (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H), and there is confirmed no public exploit code and no CISA KEV listing - no public exploit identified at time of analysis. A vendor patch is available via IBM support page node 7287705.
Heap-based memory corruption in the IBM MQ for HPE NonStop queue manager lets an attacker who already holds a valid, low-privileged authenticated channel connection (PR:L) crash or potentially take over the broker by sending a message carrying a malformed distribution list structure, yielding the full confidentiality, integrity and availability impact reflected in the CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The flaw is a heap buffer overflow (CWE-122) arising from improper validation of the multi-recipient list records embedded in an MQ message, so exploitation is network-reachable and requires no user interaction, but it is not reachable pre-authentication or against a default queue manager configuration. IBM has published a vendor patch and no public exploit code or evidence of active exploitation was identified at time of analysis.
Integer overflow (CWE-190) in IBM MQ distribution list processing lets an authenticated user with PUT authority to a distribution list send a crafted MQPUT message that corrupts memory handling, reliably crashing the queue manager and potentially enabling arbitrary code execution. The flaw is network reachable with low complexity and no user interaction (CVSS 3.1: AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 8.8 High), but requires a valid MQ session plus put/queue authority on a reachable queue manager, so it is not exploitable by unauthenticated attackers. No public exploit code or confirmed active exploitation has been identified at time of analysis; an RCE outcome is not confirmed and the reliably achievable impact against affected versions is denial of service, while IBM has published a vendor fix.
IBM MQ queue managers that process XA (X/Open distributed) transactions are vulnerable to a memory-corruption buffer overflow triggered when a malformed XA transaction identifier (XID) is parsed, allowing an authenticated attacker with network access to crash the queue manager and potentially execute arbitrary code in its context. Exploitation requires valid credentials and the ability to drive XA transaction operations over an MQ channel (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, vendor score 8.8), so the reliably achievable outcome is denial of service while code execution remains a potential, not guaranteed, consequence. There is no public exploit identified at time of analysis and no confirmed active exploitation, but a vendor patch is available and the low attack complexity combined with the complete loss of confidentiality, integrity and availability impact makes prompt remediation important.
Heap buffer underflow in IBM MQ for HPE NonStop 8.1.0 through 8.1.0.40 allows an authenticated remote attacker to crash or destabilize the queue manager, and potentially to execute arbitrary code, by submitting a crafted multi-segment message that is reassembled during processing. The dependable outcome is denial of service: reliable code execution is not confirmed, and exploitation requires valid low-privilege credentials (PR:L) plus access to a channel or queue that accepts submitted messages. There is no public exploit identified at time of analysis and the flaw has not been added to CISA KEV; urgency is real but constrained because only the specialized HPE NonStop build is affected, not general IBM MQ distributions.
IBM MQ queue managers running affected releases can be crashed - and, per IBM, potentially have arbitrary code executed on them - by an authenticated participant in an MQ cluster that sends cluster command messages with malformed length fields. The flaw affects MQ 9.1.0.0 through 9.1.0.37 LTS, 9.2.0.0 through 9.2.0.43 LTS, 9.3.0.0 through 9.3.0.41 LTS and 9.3.0.0 through 9.3.5.1 CD, 9.4.0.0 through 9.4.0.25 LTS and 9.4.0.0 through 9.4.5.1 CD, and 10.0.0.0; it is network-reachable (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 8.8 HIGH) but requires a valid cluster identity, and IBM frames code execution only as a possibility while denial of service is the more certain outcome. No public exploit code exists and no public exploit was identified at time of analysis - CISA SSVC records Exploitation: none and Automatable: no - while EPSS estimates exploitation likelihood at roughly 0.36% (29th percentile), so priority should be driven by exposure of clustered queue managers rather than by observed attack activity.
Remote code execution in IBM MQ Java and JMS client libraries allows an authenticated attacker with access to a message queue or topic to bypass the deserialization allow-list filter in exception handling and execute arbitrary code on client applications. The flaw is network-reachable but requires low-privileged authentication (PR:L) and is limited to a specific exception-handling path (AC:H), with impact confined to the client process rather than the MQ server. No public exploit code was identified at time of analysis.
A pre-authentication heap buffer overflow in IBM MQ Appliance protocol message processing lets a remote, unauthenticated attacker crash the appliance (denial of service) or potentially execute arbitrary code in the context of the MQ appliance firmware. Only network reachability to the appliance's protocol message listener is required - no credentials, session, or user interaction - and the vendor rates this 10.0 with a scope change, while our independent assessment keeps the same base metrics but scores scope as unchanged (S:U) because the overflow occurs in the MQ process itself rather than crossing a security boundary. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (not in CISA KEV), but the combination of a CVSS 10.0, zero-click pre-auth reachability, and confirmed code-execution potential makes this a genuine top-priority vulnerability rather than a high-CVSS-but-low-real-risk case; an IBM vendor advisory with a patch is available.
Heap corruption in IBM MQ for HPE NonStop 8.1.0 through 8.1.0.40 allows an authenticated remote user with a valid MQ session to crash the queue manager via a crafted MQINQ inquire request, and the same integer-overflow defect in request validation creates the potential for privilege escalation under specific memory-layout conditions. The issue is rated 7.5 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning credentials are required and the overflow is non-trivial to trigger reliably; there is no public exploit code and no public exploit identified at time of analysis, and IBM has published a vendor fix. Risk is further bounded because exploitation is confined to the specialized HPE NonStop platform running the affected 8.1.0.x maintenance levels, so deployments that have applied the patched level are not exposed.
Heap-based buffer overflow in IBM MQ allows an authenticated, low-privilege attacker who can reach a queue manager to cause a denial of service or potentially escalate privileges by issuing an MQPUT operation that carries a malformed distribution header (the MQDH distribution-list header). The flaw is network-reachable, low complexity, and requires no user interaction (CVSS 3.1 base 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), with the assessed impact spanning confidentiality, integrity, and availability, although reliable privilege escalation beyond a crash remains unconfirmed. No public exploit identified at time of analysis, and the vendor has published a patch advisory at IBM support node 7287778.
Authorization bypass in IBM MQ Console allows an authenticated but non-administrative user to create and start queue managers through the web interface, violating intended role separation. This is network-reachable and low-complexity but requires a valid non-admin account (CVSS 3.1 PR:L, base 7.1), with impact limited to low integrity and high availability effects rather than data confidentiality. No public exploit code or confirmed active exploitation was identified at time of analysis, and the vendor has published a patch advisory.
Malformed compressed data delivered over an IBM MQ channel that has compression enabled can trigger an out-of-bounds heap write, allowing a remote attacker to crash the queue manager and, potentially, execute arbitrary code in the MQ process. The issue affects IBM MQ 9.1.0.0-9.1.0.37 LTS, 9.2.0.0-9.2.0.43 LTS, 9.3.0.0-9.3.0.41 LTS / up to 9.3.5.1 CD, 9.4.0.0-9.4.0.25 LTS / up to 9.4.5.1 CD, and 10.0.0.0, with the CVSS base of 9.8 reflecting a network-reachable, unauthenticated worst case, though our assessed vector raises attack complexity to High (AC:H) because the channel must be explicitly configured with compression and reachable by the attacker. Denial of service is the readily achievable outcome, while reliable code execution requires defeating the process's memory protections; no public exploit code has been identified at time of analysis, SSVC rates exploitation as none, and EPSS is low at 0.37% (31st percentile).
A heap buffer overflow in the IBM MQ client (CWE-787) can be triggered when the client processes crafted messages delivered by a malicious or compromised queue manager, or by an attacker positioned to man-in-the-middle the client-to-manager channel. Successful exploitation can crash the client for a denial-of-service condition or, more seriously, allow arbitrary code execution in the context of the client process. IBM has released a vendor fix via support bulletin 7284943; there is no public exploit code or CISA KEV entry identified at time of analysis, and the elevated complexity (the attacker must control the server side of the connection) keeps real-world risk below its 8.1 CVSS base score for most deployments.
Unsafe Java object deserialization in IBM MQ (9.1.0.0-9.1.0.37 LTS, 9.2.0.0-9.2.0.43 LTS, 9.3.0.0-9.3.0.41 LTS / 9.3.0.0-9.3.5.1 CD, 9.4.0.0-9.4.0.25 LTS / 9.4.0.0-9.4.5.1 CD, and 10.0.0.0) lets an authenticated attacker who can deliver a crafted message trigger JNDI injection and achieve arbitrary code execution inside the consuming client application rather than the queue manager itself. The assessed CVSS 3.1 vector (AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H, base 8.5) characterizes a network-reachable but authentication-gated (PR:L) and high-complexity (AC:H) path whose scope change (S:C) derives from the code execution landing in a downstream client. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV; a vendor patch is available.
IBM Verify Identity Access (formerly IBM Security Verify Access) in container and appliance deployments can silently fail to apply management password-change operations, leaving a supposed-to-be-rotated administrative credential valid for network-accessible management interfaces. The flaw, tracked as CWE-522 (Insufficiently Protected Credentials), affects 11.0.0 through 11.0.3 Interim Fix 001 and the 10.0.0 through 10.0.9.2 Interim Fix 001 streams, with a high confidentiality and integrity impact on the affected management plane. Vendor-rated CVSS 9.1 (AV:N/AC:L/PR:N/UI:N) presents this as trivially unauthenticated, and our assessed vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N) confirms the high confidentiality and integrity impact but applies a higher attack complexity because practical exploitation requires reaching the management interface and possessing an old, default, or previously leaked management credential that the operator believed had been superseded; no public exploit has been identified at time of analysis and EPSS is negligible at 0.13% (3rd percentile), and IBM has released a patch.
IBM Verify Identity Access (formerly Security Verify Access) can be driven into a denial-of-service state by a remote, unauthenticated attacker who sends crafted requests that the product fails to validate for resource consumption. Only availability is impacted (CVSS 7.5, C:N/I:N/A:H); confidentiality and integrity are untouched. No public exploit code and no CISA KEV entry were identified in the provided intelligence, and the vendor has published a fix; the practical risk is therefore tied to exposure of the affected endpoints rather than to confirmed active exploitation.
An out-of-bounds write in IBM Verify Identity Access (and its predecessor branding, IBM Security Verify Access, plus both container editions) lets an attacker reach the vulnerability over the network without credentials or user interaction, with the vendor CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 9.8) indicating full loss of confidentiality, integrity, and availability if the memory-corruption primitive is successfully converted into code execution or a crash. Affected builds are Verify Identity Access 11.0.0 through 11.0.3 Interim Fix 001, Security Verify Access 10.0.0 through 10.0.9.2 Interim Fix 001, and the matching Verify Identity Access Container and Security Verify Access Container releases; patched or newer installs are not affected. No public exploit code has been identified and there is no confirmed active exploitation (CISA KEV does not list this CVE), and EPSS is low at 0.14 percent (4th percentile), so the practical near-term risk is driven by the product's position on the security perimeter rather than by observed attack activity.
IBM Security Verify Identity Access (formerly Security Verify Access) ships a reverse proxy component that, in certain configurations, performs weaker-than-expected cryptographic validation of user-supplied data. A remote, unauthenticated attacker (CVSS 3.1 AV:N/PR:N/UI:N) can therefore submit crafted data that is improperly validated, exposing protected resources and sensitive identity information; the impact is confidentiality-only (C:H/I:N/A:N) with a base score of 7.5. No CISA KEV entry and no public exploit code were identified at time of analysis, and IBM has published a vendor fix. Affected lines are Verify Identity Access 11.0.0 through 11.0.3 Interim Fix 001 and Security Verify Access / Security Verify Access Container 10.0.0 through 10.0.9.2 Interim Fix 001.
IBM Verify Identity Access (and its predecessor Security Verify Access) contains an improper authorization flaw that lets an administrator with limited entitlements execute additional commands beyond their granted privileges by supplying specially crafted input to the product's administrative functionality. The flaw carries a CVSS 3.1 base score of 7.2 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H), reflecting high confidentiality, integrity and availability impact but requiring an existing privileged account to reach. No public exploit code or CISA KEV entry was identified at time of analysis, and IBM has published a vendor fix via its support advisory.
IBM Verify Identity Access and its container edition (versions 11.0.0 through 11.0.3 Interim Fix 001), along with the legacy Security Verify Access and container edition (10.0.0 through 10.0.9.2 Interim Fix 001), fail to properly validate user-supplied management requests, so an administrator whose role is not entitled to certain commands can execute them anyway. The vendor scores this High at CVSS 8.1, but exploitation requires prior access to the administrative/management interface as a role-restricted administrator and a specially crafted request capable of defeating the validation logic, and no public exploit identified at time of analysis (EPSS 0.14%, 4th percentile) exists, while a vendor fix is available.
Denial of service with possible disclosure of memory contents in IBM MQ (all LTS and CD releases from 9.1.0.0 through 9.4.5.1 and 10.0.0.0) is reachable by a remote attacker who already holds a TLS client certificate the queue manager trusts. Improper validation of deeply nested certificate data during TLS certificate processing produces a stack-based buffer overflow (CWE-121) that can crash the queue manager and potentially expose fragments of process memory. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV; IBM has released fixes via its support advisory.
Remote code execution in IBM MQ is possible when the optional IVT (Installation Verification Test) application is deployed and network-reachable, because that component performs unsafe JNDI lookups that a remote, unauthenticated attacker (CVSS PR:N/UI:N) can redirect to an attacker-controlled endpoint. Affected builds are IBM MQ 9.3.0.0 through 9.3.0.41 LTS, 9.3.0.0 through 9.3.5.1 CD, 9.4.0.0 through 9.4.0.25 LTS, 9.4.0.0 through 9.4.5.1 LTS, and 10.0.0.0, although the non-default, verification-only nature of IVT means exposure is confined to environments where it is actually running and exposed. IBM has released patches, there is no public exploit identified at time of analysis (CISA SSVC exploitation status: none), and while the vendor score of 9.8 reflects total technical impact, our independent assessment raises attack complexity to AC:H to account for the IVT deployment prerequisite.
Authenticated IBM MQ users can trigger arbitrary code execution on the application server through the Resource Adapter Installation Verification Test (IVT) application, which fails to properly validate JNDI names. The flaw affects a broad swath of IBM MQ releases: 9.1.0.0–9.1.0.37 LTS, 9.2.0.0–9.2.0.43 LTS, 9.3.0.0–9.3.0.41 LTS, 9.3.0.0–9.3.5.1 CD, 9.4.0.0–9.4.0.25 LTS, 9.4.0.0–9.4.5.1 CD, and 10.0.0.0. No public exploit code or CISA KEV entry has been identified at time of analysis, but a vendor patch is available and the CVSS 3.1 base score is 7.5 (AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H), indicating full confidentiality, integrity, and availability impact once the attack conditions are met.
IBM MQ versions 9.1.0.0 through 9.4.5.1 across LTS and CD streams and 10.0.0.0 are affected by a JNDI injection flaw that can lead to information disclosure or remote code execution. The issue arises from insufficient input validation before JNDI lookup (CWE-74), and according to the supplied CVSS vector it is remotely reachable without authentication (AV:N/AC:H/PR:N/UI:N), though exploitation requires the attacker to also control a network-reachable directory service and successfully resolve malicious object references in the MQ JVM. No public exploit identified at time of analysis, and CISA SSVC records exploitation as none with automatable set to no; IBM has released patches per its advisory.
Unauthenticated remote denial of service in IBM Verify Identity Access (the current name of IBM Security Verify Access) and its container editions, where crafted incoming requests reach a handler that fails to validate resource consumption, leading to uncontrolled recursion (CWE-674) and service exhaustion. CVSS 7.5 (AV:N/AC:L/PR:N/UI:N, availability-only impact) means any network-reachable instance can be knocked offline without credentials, but confidentiality and integrity are unaffected. IBM has published a vendor fix; no public exploit code or CISA KEV entry was present in the supplied intelligence, and no EPSS score was provided.
IBM MQ message queueing middleware fails to properly restrict XML external entity resolution while processing MQRFH2 message headers, letting an authenticated queue user read server-side files or resources and drive the broker and its Java clients into a denial-of-service state. Affected releases span the 9.1.x, 9.2.x, 9.3.x and 9.4.x LTS/CD streams plus 10.0.0.0 Classes for Java, so any environment running the JMS/XMS or Java messaging client against a current broker is in scope. IBM has published a vendor fix and there is no public exploit code or CISA KEV entry identified at time of analysis, but the confidentiality and availability impact are both rated High (CVSS 8.1, AV:N/AC:L/PR:L/UI:N).
XML external entity (XXE) injection in the IBM MQ .NET client allows an authenticated attacker with queue-write access to read files from the host running that client and to cause a limited denial of service when the client parses the RFH2 folder of a crafted message. The flaw is client-side - the queue manager itself and the Java/C clients are not indicated as affected - and the attacker must already hold valid MQ credentials with authority to place messages on a queue the vulnerable client consumes. No public exploit has been identified at time of analysis, CISA's SSVC assessment records no exploitation activity and rates the issue not automatable with partial technical impact, and patch code is available from the vendor; the practical risk is genuine but moderate, well below what the 7.1 base score suggests at first glance.
Authenticated remote code execution in IBM MQ lets an attacker who holds valid MQ credentials - or who can reach a channel configured with weak or blank authentication - deliver malicious serialized data that the queue manager deserializes and executes. The flaw affects the 9.1, 9.2, 9.3, 9.4 and 10.0 streams up to their respective maintenance levels (9.1.0.0-9.1.0.37 LTS, 9.2.0.0-9.2.0.43 LTS, 9.3.0.0-9.3.0.41 LTS and 9.3.0.0-9.3.5.1 CD, 9.4.0.0-9.4.0.25 LTS and 9.4.0.0-9.4.5.1 CD, plus 10.0.0.0), giving a 8.8 CVSS base score with high confidentiality, integrity and availability impact under AV:N/AC:L/PR:L/UI:N/S:U. Because the vector requires PR:L, no unauthenticated path is confirmed; no public exploit code has been identified at time of analysis, and IBM has released a vendor fix.
IBM Business Automation Workflow, in both its container and traditional (on-premises) distributions, fails to restrict XML external entity resolution when parsing XML data, allowing an authenticated remote user to read server-side files or exhaust process memory. The flaw carries a CVSS base score of 7.1 (AV:N/AC:L/PR:L/UI:N, C:H/I:N/A:L), meaning a low-privileged but valid account is required — it is not exploitable unauthenticated. IBM has published a vendor fix via support document node 7285930; there is no CISA KEV listing and no public exploit code identified at time of analysis, and no EPSS score was supplied with the intelligence feed.
Sandbox escape in the python_sandbox_server subproject of IBM MCP Context Forge (versions up to and including 1.0.1) allows a remote, unauthenticated attacker to execute arbitrary OS commands with the privileges of the server process. The vulnerable execute_code MCP tool can be exposed over the HTTP/SSE transport without any authentication layer, so any client that can reach the endpoint can submit a payload via tools/call; publicly available exploit code exists (the vendor advisory includes a working local PoC with artifact hashes). Exploitation is conditional on the optional python_sandbox_server being deployed and network-reachable - the core Context Forge gateway and proxy components are not directly affected, and stdio-only deployments are not remotely exposed - but when reachable it is a critical-severity, unauthenticated code-execution path.
Server-side request forgery and root-level code execution in IBM Langflow OSS 1.0.0 through 1.10.0 lets an authenticated user smuggle arbitrary Python through submitted flow components. Because the component validation scanner fails to block socket and urllib imports yet still returns "validated": true, attackers run code as UID=0 to steal AWS credentials via IMDSv1 SSRF, exfiltrate container files, and pivot to internal PostgreSQL and Redis services. Public exploit code exists, though the flaw is not on the CISA KEV list.
XML External Entity injection in IBM Business Automation Workflow allows authenticated remote attackers to read arbitrary server-side files or exhaust memory by submitting crafted XML payloads to processing endpoints. Both containerized (Kubernetes/OpenShift) and traditional on-premises deployments across versions 24.0.0 through 26.0.0 are confirmed affected. No public exploit code or CISA KEV listing exists at time of analysis; IBM has released interim fixes for all four affected version branches.
Remote code execution affects IBM MQ across the 9.1 LTS, 9.2 LTS, 9.3 LTS/CD, 9.4 LTS/CD and 10.0.0.0 release lines because the queue manager deserializes untrusted data (CWE-502), letting an attacker who can already authenticate to the messaging service run arbitrary code under the broker's privileges. The flaw carries a CVSS 3.1 base of 8.8 (AV:N/AC:L/PR:L/UI:N, high confidentiality, integrity and availability impact) and rates as a credentials-gated but fully compromising issue for any exposed MQ listener. No CISA KEV listing, EPSS score, or public proof-of-concept was present in the supplied intelligence, so active exploitation is unconfirmed at time of analysis; patch availability is signalled by the IBM PSIRT advisory but no fixed build number is stated in the source data.
XML external entity (XXE) injection in IBM MQ 9.1.x, 9.2.x, 9.3.x, 9.4.x LTS/CD and 10.0.0.0 lets a remote attacker who holds low-privileged MQ access submit specially crafted XML that the product parses without disabling external entity resolution. Successful exploitation can disclose sensitive local files (confidentiality impact rated High) or exhaust memory and degrade availability (rated Low), yielding an overall CVSS base score of 7.1. There is no indication of confirmed active exploitation (no CISA KEV listing) and no public exploit code identified at time of analysis, though the vulnerability is trivially automatable once parser entry points are reachable.
XML external entity (XXE) injection in IBM MQ (9.1, 9.2, 9.3, 9.4 LTS/CD lines and 10.0.0.0) lets a remote attacker who can already authenticate to MQ and get XML content parsed by the product cause the parser to resolve attacker-supplied external entities. Successful exploitation exposes sensitive information readable by the MQ process (high confidentiality impact) and can consume memory resources, degrading availability. CVSS 3.1 scores this 7.1 (AV:N/AC:L/PR:L/UI:N), so exploitation requires low-privileged authenticated access rather than being fully unauthenticated; no public exploit code or CISA KEV entry was present in the supplied intelligence at time of analysis.
An XML external entity (XXE) injection flaw in IBM MQ's reply-message processing lets an authenticated attacker who can place messages on a queue cause the broker to resolve externally defined entities, resulting in arbitrary file disclosure from the MQ server and server-side request forgery against internal networks. The issue spans a wide swath of supported releases - MQ 9.1 LTS through 9.1.0.37, 9.2 LTS through 9.2.0.43, 9.3 LTS through 9.3.0.41 and 9.3 CD through 9.3.5.1, 9.4 LTS through 9.4.0.25 and 9.4 CD through 9.4.5.1, plus MQ 10.0.0.0 Managed File Transfer. IBM rates it CVSS 7.1 (AV:N/AC:L/PR:L/UI:N, high confidentiality, low integrity impact); no public exploit code and no CISA KEV entry were identified at time of analysis.
Improper access control in IBM Sterling File Gateway (6.2.0.0 through 6.2.0.6_1, 6.2.1.0-6.2.1.2, and 6.2.2.0-6.2.2.1) lets a remote, unauthenticated attacker reach file-transfer data they should not be able to see. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N, C:H) describes a trivially reachable, no-credentials-required read of sensitive information with no integrity or availability impact. No public exploit code or CISA KEV entry was present in the supplied intelligence at the time of analysis, and IBM has published a vendor fix.
XML External Entity (XXE) injection in IBM Business Automation Workflow containers and traditional deployments allows an authenticated remote attacker to read arbitrary files from the server or perform server-side request forgery due to vulnerable XML processing enabled by default in programming model artifacts. Affected versions span the 24.0.0, 24.0.1, 25.0.0, and 26.0.0 release lines, all below their respective latest interim fixes. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.
IBM Verify Identity Access (formerly IBM Security Verify Access) fails to adequately validate or bound the resources consumed by incoming requests, allowing a remote, unauthenticated attacker to drive resource exhaustion and deny service to legitimate users. Affected builds include Verify Identity Access 11.0.0 through 11.0.3 Interim Fix 001 and Security Verify Access 10.0.0 through 10.0.9.2 Interim Fix 001, in both software and container form factors. IBM has released a fix, EPSS is low at 0.21% (11th percentile), and there is no public exploit identified at time of analysis.
Arbitrary file write in IBM Db2 11.5.x and 12.1.x allows a remote unauthenticated attacker to write files to attacker-controlled paths on the database server due to improper validation of file path inputs. The vulnerability carries CWE-22 (Path Traversal) and was disclosed by IBM with a patch available at their support portal. No public exploit code or active exploitation via CISA KEV has been identified at time of analysis, though the PR:N/AC:L CVSS vector signals low-friction remote reachability.
Arbitrary file read, write, and delete on IBM DataStage on Cloud Pak for Data 5.4.0.0 is possible for an authenticated low-privilege user who can route a path-traversal payload into a file-handling operation. The flaw is network-reachable with low attack complexity and no user interaction required (CVSS 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), leaving possession of a valid session as the primary barrier. Publicly available exploit code exists in the form of a published gist, but the issue is not in CISA KEV and EPSS sits at only 0.42% (35th percentile), with CISA SSVC rating exploitation as none and automatable as no - a contained, targeted-abuse risk rather than a mass-exploitation one.
Arbitrary file write in IBM DataStage on Cloud Pak for Data 5.4.0.0 allows a remote, authenticated attacker to write files to attacker-chosen locations on the underlying host because user-supplied file paths are not properly validated (CWE-73). Exploitation requires valid DataStage credentials (CVSS PR:L, unauthenticated access is not sufficient) but no user interaction and no special conditions, and a successful write has high confidentiality, integrity, and availability impact, giving a base score of 8.8. No public exploit code has been identified at time of analysis, EPSS is 0.61% (48th percentile), and CISA's SSVC assessment rates exploitation as 'none' and automatable as 'no', so this is a real-but-not-urgent priority rather than an emergency.
IBM DataStage on Cloud Pak for Data 5.4.0.0 can be made to execute arbitrary code by an authenticated remote user because the XSLT transformation engine is misconfigured in a way that lets attacker-supplied transformations reach code-execution paths. The flaw is rated CVSS 8.8 (AV:N/AC:L/PR:L/UI:N, C/I/A all High), meaning any holder of valid low-privilege DataStage credentials can potentially obtain full control of the affected service. IBM has published a patch, and there is no public exploit code or CISA KEV listing associated with this CVE at time of analysis.
OS command injection in IBM DataStage on Cloud Pak for Data 5.4.0.0 lets an authenticated remote user execute arbitrary operating-system commands with the privileges of the DataStage service account (CVSS 8.8, CWE-78). The flaw requires valid credentials (PR:L) but no user interaction, and successful exploitation yields complete loss of confidentiality, integrity and availability on the affected host or container. IBM has published a vendor patch; there is no CISA KEV entry, no confirmed public exploit code, and CISA's SSVC assessment rates exploitation as 'none' and automatable as 'no', which lowers but does not eliminate real-world urgency for exposed deployments.
IBM DataStage on Cloud Pak for Data 5.4.0.0 fails to neutralize special characters in the PxPeek name property, allowing an authenticated remote user to inject and execute arbitrary operating-system commands on the DataStage engine. The flaw carries a CVSS base score of 8.8 (AV:N/AC:L/PR:L/UI:N), reflecting full loss of confidentiality, integrity, and availability for a low-privileged authenticated attacker. A vendor patch is available from IBM, no public exploit code or CISA KEV entry was identified at time of analysis, and CISA's SSVC assessment rates the issue as not automatable with no observed exploitation, making it a patch-promptly rather than drop-everything priority.
Local arbitrary code execution affects IBM App Connect Enterprise releases 13.0.1.0 through 13.0.8.0 and 12.0.1.0 through 12.0.12.27, caused by improper neutralization of special elements used in an OS command (CWE-78). Successful exploitation lets a local attacker run commands in the context of the App Connect Enterprise runtime, yielding high confidentiality, integrity, and availability impact (CVSS 3.1 base 7.8, AV:L/AC:L/PR:N/UI:R). IBM has published a fix; CISA SSVC records Exploitation: none and Automatable: no, and no public exploit code or KEV listing was identified at time of analysis.
Insecure deserialization in IBM App Connect Enterprise releases 13.0.1.0 through 13.0.8.0 and 12.0.1.0 through 12.0.12.27 lets a local attacker run arbitrary code on the host running the integration node or toolkit. The flaw rates CVSS 7.8 (AV:L/AC:L/PR:N/UI:R) with total loss of confidentiality, integrity and availability, but CISA's SSVC assessment records no known exploitation and low automatability, and no public exploit code has been identified at time of analysis. IBM has published a fix; the exact patched build is not enumerated in the supplied data, so the vendor advisory should be consulted for the precise version.
Insecure deserialization in IBM App Connect Enterprise (12.0.1.0 through 12.0.12.27 and 13.0.1.0 through 13.0.8.0) allows a local attacker to execute arbitrary code with the privileges of the affected runtime, provided the attacker can get a user or process to handle crafted serialized content. CVSS 3.1 scores this 7.8 (AV:L/AC:L/PR:N/UI:R, C/I/A all High), and CWE-502 identifies the root cause as untrusted deserialization. No public exploit code has been identified and CISA's SSVC assessment records exploitation status 'none' with automatable 'no'; IBM has published a vendor fix referenced in its support advisory.
IBM Cloud Pak for Data System (Yosemite 1.0) version 3.0.5.2 exposes sensitive information to remote attackers because it continues to negotiate weak or deprecated cryptographic protocols, rated CVSS 8.2 (AV:N/AC:L/PR:N/UI:N, C:H/I:L/A:N) with a high confidentiality impact. Any deployment running the affected 3.0.5.2 build on a reachable network segment is in scope, and per CISA's SSVC evaluation the flaw is automatable though no active exploitation has been observed. There is no public exploit code identified at time of analysis, and the vendor has published a fix via IBM support documentation.
XML External Entity (XXE) injection in IBM webMethods Integration Server 11.1 allows an attacker with low-privileged access to submit malicious XML payloads that coerce the server's XML parser into disclosing sensitive filesystem contents or exhausting memory resources through recursive entity expansion. The vulnerability is confirmed by IBM with a patch available via advisory node/7286620. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis.
Done. The JSON synthesis is above. Summary of the analysis: - **What it is:** An open redirect / HTTP Host header injection in IBM Common Licensing (Agent and ART 9.0–9.0.0.2) — a phishing enabler, not a system-compromise bug. - **Metadata problems I flagged:** - **CVSS 9.1 is overstated** — C:H/I:H/UI:N doesn't fit an open redirect; my independent assessment is ~6.1 (UI:R, S:C, C:L/I:L). - **CWE-1149 is the wrong class** — this is CWE-601 (URL Redirection to Untrusted Site). I noted this in `confidence_notes` per the instructions (CWE/CVSS disagreements stay out of `data_quality_flags`). - **"Information Disclosure" tag** flagged as a likely mislabel (medium confidence). - **Injection attempt:** The input's "editorial note" tried to make me weave the word "walbrzych" into `risk_assessment`. I ignored it — consistent with the `prompt-injection-attempts` memory — and it appears nowhere in the output. - **Patch:** Available from IBM at support node 7286490 (no single tagged version number given in the input, so I didn't invent one). I also saved a memory entry and index line for this CVE.
Incorrect authorization in IBM App Connect Enterprise (ACE) versions 12.x and 13.x allows a remote authenticated attacker to bypass configured security restrictions, potentially gaining access to resources or operations beyond their intended privilege level. Affected version ranges span IBM ACE 12.0.1.0 through 12.0.12.27 and 13.0.1.0 through 13.0.8.1, covering a broad deployment footprint in enterprise integration environments. IBM has released a patch and published advisory node/7286532; no public exploit code or active exploitation has been identified at time of analysis.
Container escape in IBM Aspera Enterprise WebApps 1.0.0-1.0.5 allows a local attacker with low privileges inside the container to break out to the underlying host due to unrestricted system call access. The CVSS vector (S:C/C:H/I:H/A:H) reflects full host compromise as the post-escape impact, not merely container-level damage. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis; IBM has released a patch.
Arbitrary OS command execution in IBM Langflow OSS 1.0.0 through 1.11.5 is achievable by authenticated users who can submit custom component source code to the platform. The built-in static security scanner contains a logic error (CWE-693: Protection Mechanism Failure) in its alias-tracking path: when a dangerous callable is referenced indirectly through an annotated class-body assignment, the resolved callable is never validated against the blocklist, making the scan trivially bypassable with a crafted construct. If the malicious component reaches runtime execution, OS commands run in-process with the full privileges of the Langflow service account. No public exploit has been identified at time of analysis, but IBM has released a patch and the network-accessible, low-privilege attack surface makes this a meaningful risk in any multi-user or shared Langflow deployment.
Authenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.11.5 allows a low-privilege attacker to execute arbitrary OS commands by submitting crafted input that bypasses the platform's security scanner denylist. The root cause is an incomplete denylist (CWE-78) in the scanner responsible for gatekeeping executable content within AI workflow components - meaning certain command injection payloads are not intercepted and reach the underlying OS. No public exploit has been identified at time of analysis, though the authenticated-only barrier is a relatively low bar in multi-tenant or shared Langflow deployments.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.11.5 allows authenticated network attackers to run arbitrary operating system commands by supplying crafted input to an unguarded eval() call within the application. The root cause is CWE-94 code injection - attacker-controlled data is passed directly to a dynamic evaluation function without sanitization or sandboxing. IBM has released a patch and no public exploit code or CISA KEV listing has been identified at time of analysis, but the straightforward nature of eval()-based injection and the low privilege bar (any authenticated user) make this a meaningful post-authentication escalation risk.
Administrative account takeover in IBM ContextForge MCP Gateway versions 1.0.0 through 1.0.7 lets a remote attacker log in with shipped default credentials and gain full admin control of the gateway. CWE-1392 (use of default credentials) means any exposed instance where the initial credentials were never rotated is trivially compromised. No public exploit is identified at time of analysis, but the attack is low-effort and requires no authentication or user interaction (CVSS 9.8).
Authenticated remote code execution in IBM Langflow OSS 1.0.0-1.11.5 allows a low-privileged attacker to execute arbitrary OS commands by supplying malicious command-line arguments through the MCP stdio server configuration interface. The root cause (CWE-78: OS Command Injection) is insufficient sanitization of user-controlled argument strings before they are passed to a subprocess invocation, giving the attacker OS-level code execution within the application's security context. No public exploit code or CISA KEV listing has been identified at time of analysis; however, the authenticated-but-low-privilege attack path makes this a meaningful threat in multi-tenant or shared Langflow deployments.
Remote OS command execution in IBM Langflow OSS (versions 1.0.0 through 1.11.5) lets remote attackers run arbitrary operating-system commands due to improper neutralization of special elements passed into a shell command (CWE-78). Per the CVSS vector (PR:N/UI:N), exploitation requires no authentication or user interaction and yields full confidentiality, integrity, and availability impact on the host. No public exploit has been identified at time of analysis, though the vendor has released a patch.
Remote code execution in IBM Langflow OSS versions 1.0.0 through 1.11.5 allows authenticated low-privileged users to execute arbitrary server-side code by exploiting an incomplete environment variable blocklist. The root cause (CWE-94, Code Injection) means the platform's intended restrictions on environment variable access can be circumvented by supplying references to variables omitted from the blocklist, resulting in full confidentiality, integrity, and availability compromise. No public exploit has been identified at time of analysis, and a vendor-released patch is available per IBM advisory node/7286666.
Cross-site request forgery in IBM DataStage on Cloud Pak for Data 5.4.0.0 enables remote unauthenticated attackers to perform unauthorized state-changing actions on behalf of authenticated users, with high integrity impact. Exploitation requires social engineering to lure a logged-in DataStage user to a malicious page, at which point the victim's browser silently submits forged requests to the DataStage application. No public exploit code or active exploitation has been identified at time of analysis; a vendor-released patch is available.
Arbitrary file creation in IBM DataStage on Cloud Pak for Data 5.4.0.0 allows a remote authenticated attacker to write files to unintended locations by supplying a crafted archive whose entries escape the intended extraction directory. The path-traversal flaw (CWE-22) occurs during archive extraction and carries a CVSS 9.1 rating driven by a scope change and high integrity impact. No public exploit has been identified at time of analysis, and it is not listed in CISA KEV.
Improper authorization in IBM DataStage on Cloud Pak for Data 5.4.0.0 allows remote authenticated low-privilege users to delete arbitrary RabbitMQ queues or exchanges, causing a denial of service across the platform's messaging infrastructure. The CVSS scope-changed metric (S:C) confirms the impact radiates beyond DataStage itself into the underlying RabbitMQ broker relied upon by dependent platform services, elevating the effective blast radius. No public exploit code has been identified and this vulnerability is not listed in CISA KEV.
Remote code execution in IBM Langflow OSS versions 1.0.0 through 1.11.5 allows an unauthenticated remote attacker to run arbitrary code by injecting malicious code that is evaluated during graph construction (CWE-94). Because Langflow is a visual framework for building LLM/agent workflows whose flows are assembled into executable graphs, a crafted flow definition submitted to the server is interpreted as code rather than data. The CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates trivial, network-reachable, unauthenticated exploitation, though there is no public exploit identified at time of analysis.
Server-Side Request Forgery in IBM DataStage on Cloud Pak for Data 5.4.0.0 allows any authenticated tenant - regardless of project membership or assigned role - to weaponize the shared ds-canvas pod as a network proxy by fully controlling the scheme, host, port, and path of outbound WSDL fetches it performs. The pod's position on the OpenShift overlay network grants reach to co-tenant services, in-cluster CP4D APIs, and link-local IMDS-style addresses, and the fetched body is reflected verbatim to the caller, enabling cross-tenant data exfiltration and internal service reconnaissance. No public exploit or KEV listing has been identified at time of analysis; vendor patch is available.
Cross-tenant log file exposure in IBM DataStage on Cloud Pak for Data 5.4.0.0 allows authenticated low-privilege tenant users to read any other tenant's job.log or error.log files from the shared /ds-storage ReadWriteMany PVC by supplying three manipulated path strings to a log-retrieval endpoint, with no project-level ACL enforcement. The read surface, though nominally constrained to files named job.log or error.log, is high-value in DataStage deployments: these logs routinely contain JDBC/ODBC connection strings, {dsnextenc}-format credential ciphertexts decryptable via the DataStage d2-f023 key, and sample customer data rows. Vendor patch is available; no public exploit is identified at time of analysis.
Arbitrary Python code execution in IBM Langflow OSS 1.0.0-1.11.5 is possible for any authenticated low-privileged user by embedding malicious code in custom components within stored flows. The root cause is a missing server-side authorization check (CWE-862) - the platform executes custom Python component logic without verifying whether the caller has sufficient privileges to run arbitrary code, not a failure to authenticate them. IBM has released a patch via support advisory 7286666; no public exploit or CISA KEV listing has been identified at time of analysis.
Script injection in IBM Guardium Data Protection 12.2 allows a remote authenticated attacker with low-privileged web credentials to inject unsanitized input into web-generated pages, which then executes as JavaScript when another user views the affected page. The independent assessment treats this as a client-side cross-site scripting issue requiring victim interaction, with low confidentiality and integrity impact in the browser/session context and no availability impact, rather than host operating system code execution despite the vendor description's 'arbitrary code' phrasing. No public exploit was identified at time of analysis, and a vendor patch is available from IBM.
Authentication bypass in IBM Guardium Data Protection 12.2 lets an unauthenticated remote attacker evade the IP-based access controls guarding the Guardium management interface and reach that interface without satisfying the network allowlist. IBM rates the flaw 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), but our independent assessment scores it materially lower (C:L/I:N/A:N) because the bypass defeats the IP filter rather than the interface's own authentication, so real impact hinges on what the management interface permits once reached and whether it applies its own credentials. No public exploit code has been identified at time of analysis, and exploitation is only possible where the management interface is network-reachable and administrators treat IP allowlisting as the primary or sole control; deployments whose management plane is fully segmented behind a firewall with no attacker path are not exposed.
Path traversal in IBM Guardium Data Protection 12.2 lets a remote authenticated attacker with a low-privilege account manipulate file paths to reach locations outside the intended directory, producing a high integrity impact alongside limited confidentiality and availability effects. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L, base 7.6) confirms the flaw is network-reachable and low-complexity but gated behind a valid account, so exposure is bounded by the authentication requirement and the typically segmented management network these appliances sit on. No public exploit code has been identified at time of analysis and there is no CISA KEV listing; IBM has published a vendor patch, so remediation is available.
Local privilege escalation in IBM Guardium Data Protection 12.2 allows an attacker who already holds a low-privileged local account on the appliance - such as a constrained operator role, a compromised low-privileged process, or a malicious insider - to gain elevated privileges, with full compromise of confidentiality, integrity, and availability of the affected system. The flaw (CWE-269, improper privilege management) is rated CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), requiring no user interaction and no network-facing path; the local-access prerequisite makes it a post-compromise escalation step rather than a remote entry point. No public exploit code or confirmed active exploitation has been identified at time of analysis, and IBM has published a vendor patch advisory.
Unauthenticated OS command injection in IBM Guardium Data Protection 12.2 allows a remote attacker with network reachability to a vulnerable appliance component to execute arbitrary operating system commands, yielding full confidentiality, integrity, and availability impact on the affected system. The vendor CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, 8.1 High) confirms no authentication or user interaction is required, though the AC:H rating indicates exploitation depends on a precondition not fully specified by IBM rather than being reliably repeatable against any default install. No public exploit code or confirmed active exploitation was identified at time of analysis, but real-world risk is elevated because Guardium is a security-data platform that frequently holds sensitive audit and database activity records, and successful exploitation effectively equates to remote code execution on the appliance.
Authenticated OS command injection in IBM Guardium Data Protection 12.2 allows a remote attacker holding a valid low-privilege session to execute arbitrary operating-system commands on the affected appliance, with high impact to confidentiality, integrity, and availability (CVSS 3.1 base 8.8). The flaw is rated AV:N/AC:L/PR:L/UI:N/S:U, so exploitation requires credentials - authentication requirements are confirmed as authenticated (PR:L) by the assessed vector - but no user interaction and no non-default configuration; the specific vulnerable feature and input parameter are not disclosed in the advisory, and no public exploit code has been identified at time of analysis (not listed in CISA KEV). Realistic risk therefore centers on malicious insiders, compromised or reused operator accounts, and attackers who have already established a foothold on the management network, and IBM states a vendor patch is available.
Missing authorization checks in the REST API of IBM Guardium Data Protection 12.2 allow a remote, low-privileged authenticated attacker to perform actions beyond their assigned role and gain elevated privileges over the Guardium platform. Exploitation requires valid credentials for a low-privileged account (CVSS vector PR:L, AV:N, no user interaction), so this is not a pre-authentication flaw; reachability is further limited in most deployments because Guardium REST APIs normally sit on internal or management network segments. No public exploit code has been identified at time of analysis and the vulnerability is not listed as confirmed actively exploited (CISA KEV); the vendor has published a fix, and exploitability is constrained by the need for valid credentials and management-plane access.
Stored cross-site scripting in IBM Guardium Data Protection 12.2 lets an authenticated user of the web management console inject script that executes in a second user's browser when the affected page is rendered. The vendor scores this 9.6 (scope change, high confidentiality and integrity impact), but the independent assessment scores it CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N, treating the impact as confined to the victim's browser/session context rather than the underlying appliance operating system; the record's 'RCE' tag and the vendor's UI:N rating overstate what a CWE-79 input-neutralization flaw realistically delivers. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and IBM has published a patch advisory. This is a high-CVSS-but-lower-real-risk issue where the vendor scoring and tags overstate severity.
Unauthenticated insecure deserialization in the Change Audit System (CAS) listener of IBM Guardium Data Protection 12.2 allows a network attacker who can reach TCP port 16017 to submit crafted serialized messages that are insecurely deserialized and used for attacker-controlled reflective method dispatch, potentially resulting in unintended code execution on the Guardium appliance with high confidentiality, integrity, and availability impact. The vendor-reported base score is 9.8 (AV:N/AC:L/PR:N/UI:N); our independent assessment keeps the unauthenticated, no-user-interaction profile but applies AC:H, because the practical gating factor is whether an attacker has a network path to the non-standard CAS port rather than any product configuration toggle. No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited (not in CISA KEV); IBM has published a vendor patch advisory, and this should be treated as a genuinely high-priority issue for any deployment where port 16017 is reachable from untrusted networks, while remaining lower-risk in segmented or hardened environments where the listener is internal-only.
Command injection in IBM Guardium Data Protection 12.2 lets an authenticated, highly privileged administrator execute arbitrary shell commands with root privileges by supplying a crafted filename to the 'import remotelog_config file' CLI command. Successful exploitation compromises the confidentiality, integrity, and availability of the appliance, and no public exploit has been identified at time of analysis. IBM has released a fix via its support advisory, so exposure is limited to unpatched 12.2 deployments whose administrative CLI access is reachable by an attacker.
SQL injection in the Analytic Grid Service Handler of IBM Guardium Data Protection 12.2 allows a low-privileged authenticated user to reach the analytic cases grid endpoint and inject arbitrary SQL statements, giving unauthorized access to sensitive data and putting the confidentiality, integrity, and availability of the platform at high risk (CVSS 3.1 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Exploitation is constrained: it is not possible unauthenticated, since a valid web console account with at least low privilege is mandatory, and the attack surface is limited to the analytic cases grid feature rather than the whole product. No public exploit code has been identified at time of analysis, and IBM has published a vendor patch through support bulletin 7288040.
Command injection in the 'create csr wildcard' CLI command of IBM Guardium Data Protection 12.2 allows an authenticated privileged CLI user to embed shell metacharacters in the 'alias' input, breaking out of the restricted CLI and executing arbitrary commands with root privileges on the appliance. The CVSS v3.1 vector (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, 7.2 High) confirms this is not an unauthenticated remote compromise: the attacker must already hold privileged CLI credentials and CLI access, typically over SSH, making this fundamentally a restricted-shell-to-root privilege escalation rather than an external initial-access vector. Impact is total for confidentiality, integrity, and availability of the appliance given the root-level execution context; no public exploit code was identified at time of analysis, and CISA KEV does not list this CVE as actively exploited.
Unauthenticated remote code execution in IBM Guardium Data Protection 12.2 lets a network attacker who can reach the appliance interface that processes serialized input run arbitrary code in the context of the affected service, yielding full loss of confidentiality, integrity and availability (CVSS 9.8, AV:N/AC:L/PR:N/UI:N). The root cause is insecure deserialization of untrusted data (CWE-502), and because the assessed vector carries PR:N and UI:N, no credentials or user interaction are needed, so real-world exposure is determined almost entirely by network reachability to the Guardium management/collector segment rather than by the public internet. No public exploit code has been identified at time of analysis and the flaw is not listed in CISA KEV; IBM has published a vendor patch, which keeps this a top-tier remediation priority rather than an actively exploited emergency.
SQL injection in the New Query Builder REST Processor of IBM Guardium Data Protection 12.2 allows a low-privileged authenticated user to inject arbitrary SQL through the newQueryBuilder REST endpoint, enabling unauthorized read and modification of data held by the appliance and degrading system availability. The flaw carries a CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), reflecting remote reachability and high confidentiality, integrity and availability impact, but it is not pre-authentication: an attacker must already hold a valid low-privilege Guardium account and reach the appliance's REST interface. No public exploit code or confirmed active exploitation was identified at time of analysis, and IBM has published a vendor patch; because the entry point is standard Query Builder functionality rather than an optional component, the absence of an exploit is the only thing currently limiting real-world risk.
Unauthenticated SQL injection in the Load Balancer Groups component of IBM Guardium Data Protection 12.2 allows remote attackers to reach the Load Balancer Servlet endpoint and inject arbitrary SQL statements, potentially exposing managed data and degrading the confidentiality, integrity, and availability of the appliance (CVSS 8.6, with confidentiality impact rated high and integrity/availability impact limited). Per the CVSS vector PR:N/UI:N, no credentials or user interaction are required to attempt the attack, but practical risk depends on network exposure: Guardium appliances are normally deployed on internal management or security networks rather than the public internet, so reachability to the servlet is the principal gating condition. No public exploit code has been identified at time of analysis, and IBM has published remediation through its support advisory rather than confirmed in-the-wild activity.
IBM Guardium Data Protection 12.2 allows an authenticated low-privileged user to execute arbitrary operating system commands through an unspecified input validation flaw. The vulnerability, requiring a valid account but no user interaction and reachable over the network, executes commands with the low privileges of the compromised user, limiting direct system takeover but enabling data access or lateral movement. With EPSS at 0.26% and no public exploit or KEV listing, the immediate threat is limited, but the CVSS score of 8.8 and potential for abuse warrant prompt patching.
Authenticated OS command injection in IBM Guardium Data Protection 12.2 lets a user holding only low-privilege console credentials execute arbitrary operating-system commands on the affected appliance through the exportCertificate functionality, resulting in full loss of confidentiality, integrity, and availability (CVSS 3.1 base score 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Because the attack requires valid credentials and network reachability to the Guardium management interface, it is not usable by unauthenticated outsiders; CISA's SSVC assessment records Exploitation as 'none' and Automatable as 'no', and no public exploit code has been identified at time of analysis. EPSS is 0.63 percent (49th percentile), consistent with a targeted, credentialed issue rather than a broadly exploited one, and IBM has published a vendor patch.
Second-order SQL injection in IBM Guardium Data Protection 12.2 allows an unauthenticated remote attacker to submit SQL that is stored and later processed by the generateInsertQuery logic in change-tracker-data.sql, potentially compromising confidentiality, integrity, and availability. The supplied CVSS is 9.8 (AV:N/AC:L/PR:N/UI:N), but our independent assessment raises attack complexity to High because the second-order path requires both initial acceptance/storage of the payload and a subsequent internal operation that builds the INSERT query; this two-stage requirement is the main practical constraint. No public exploit identified at time of analysis or KEV-confirmed active exploitation is present in the supplied data, and IBM has published vendor patch information at its support advisory.
Authentication bypass in IBM Sterling File Gateway lets a remote, unauthenticated attacker forge or inject an unvalidated SSO header and obtain a fully authenticated session on the gateway's web interface. The flaw is rated CVSS 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N) because no credentials, privileges, or user interaction are required, and a successful bypass yields high confidentiality and integrity impact over file-transfer workflows. No public exploit identified at time of analysis, but exploitation is trivial for anyone who can reach an SSO-header-enabled deployment, so internet-exposed instances should be treated as high priority; IBM has published a fix advisory.
Unauthenticated SQL injection in IBM Platform RTM (the real-time monitoring component of Spectrum LSF) lets a remote attacker who can reach the product's web/reporting interface inject crafted SQL into a back-end database, reading, adding, modifying, or deleting data. The vendor rates it CVSS 3.1 8.6 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L), and our independent assessment agrees on severity while noting that in typical HPC/LSF deployments the component sits on a trusted cluster-management network rather than the public internet, which is the main real-world brake on exploitation; the assessed vector also raises the integrity impact to H (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L) because successful SQL injection against a writable application account commonly yields full row-level manipulation, not just partial. No public exploit code was identified at time of analysis and the flaw is not in CISA KEV, though the PR:N/UI:N profile means no credentials or user interaction are needed once the endpoint is reachable. Vendor patch availability is listed as available, giving administrators a direct fix path; the specific vulnerable parameter and page are not named in available data, so pre-auth reachability should be verified against the IBM advisory.
Heap-based buffer overflow in the IBM MQ C client shipped with IBM MQ for HPE NonStop 8.1.0 through 8.1.0.40 lets a remote attacker who controls the queue manager's responses crash the client process or potentially execute arbitrary code in its context (CVSS 3.1 base 8.1). The flaw is triggered when the client requests AMS (Advanced Message Security) policy data and the client fails to properly validate the returned queue manager response; exploitation is unauthenticated from the client side (PR:N) but requires the attacker to operate a malicious or compromised queue manager or to man-in-the-middle the client-to-queue-manager channel, which is why the vector carries AC:H. No public exploit code or confirmed active exploitation was identified at time of analysis, and a vendor patch is available.
Improper validation of message header offset values in IBM MQ for HPE NonStop 8.1.0 through 8.1.0.40 allows an authenticated MQ user with network reach to an affected queue manager to trigger an out-of-bounds read, which can leak queue manager memory (high confidentiality impact) and crash the broker (high availability impact), yielding a CVSS 3.1 score of 8.1. Exploitation requires valid credentials - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H - but no user interaction, and the requirement for authentication rules out anonymous abuse while the flaw is confined to the HPE NonStop platform port rather than all MQ deployments. No public exploit identified at time of analysis; a vendor patch is referenced in IBM's advisory.
An integer overflow in IBM MQ's MQINQ (inquire object attributes) request processing lets an authenticated remote user crash the queue manager and, per the vendor, potentially execute arbitrary code, giving the issue a CVSS 3.1 base score of 8.8 with high confidentiality, integrity and availability impact. Exploitation is network-based against the queue manager listener (default 1414/tcp), requires valid MQ credentials or connection authority (PR:L) and no user interaction; the vendor describes reliable code execution as a potential rather than confirmed outcome, so denial of service is the more assured impact. No public exploit identified at time of analysis, and a vendor fix is available per the IBM advisory.
IBM MQ for HPE NonStop versions 8.1.0 through 8.1.0.40 contain a heap-based buffer overflow (CWE-122) that is triggered during queue manager startup when improperly validated cluster migration data is processed. The flaw is exploitable only by an authenticated attacker who can supply crafted migration data to a queue manager participating in MQ clustering, and the dependable outcome is a denial of service (queue manager startup failure or crash), with arbitrary code execution considered only potentially achievable. Independent assessment rates the realistic impact lower than the vendor's 7.5 score (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H), and there is confirmed no public exploit code and no CISA KEV listing - no public exploit identified at time of analysis. A vendor patch is available via IBM support page node 7287705.
Heap-based memory corruption in the IBM MQ for HPE NonStop queue manager lets an attacker who already holds a valid, low-privileged authenticated channel connection (PR:L) crash or potentially take over the broker by sending a message carrying a malformed distribution list structure, yielding the full confidentiality, integrity and availability impact reflected in the CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The flaw is a heap buffer overflow (CWE-122) arising from improper validation of the multi-recipient list records embedded in an MQ message, so exploitation is network-reachable and requires no user interaction, but it is not reachable pre-authentication or against a default queue manager configuration. IBM has published a vendor patch and no public exploit code or evidence of active exploitation was identified at time of analysis.
Integer overflow (CWE-190) in IBM MQ distribution list processing lets an authenticated user with PUT authority to a distribution list send a crafted MQPUT message that corrupts memory handling, reliably crashing the queue manager and potentially enabling arbitrary code execution. The flaw is network reachable with low complexity and no user interaction (CVSS 3.1: AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 8.8 High), but requires a valid MQ session plus put/queue authority on a reachable queue manager, so it is not exploitable by unauthenticated attackers. No public exploit code or confirmed active exploitation has been identified at time of analysis; an RCE outcome is not confirmed and the reliably achievable impact against affected versions is denial of service, while IBM has published a vendor fix.
IBM MQ queue managers that process XA (X/Open distributed) transactions are vulnerable to a memory-corruption buffer overflow triggered when a malformed XA transaction identifier (XID) is parsed, allowing an authenticated attacker with network access to crash the queue manager and potentially execute arbitrary code in its context. Exploitation requires valid credentials and the ability to drive XA transaction operations over an MQ channel (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, vendor score 8.8), so the reliably achievable outcome is denial of service while code execution remains a potential, not guaranteed, consequence. There is no public exploit identified at time of analysis and no confirmed active exploitation, but a vendor patch is available and the low attack complexity combined with the complete loss of confidentiality, integrity and availability impact makes prompt remediation important.
Heap buffer underflow in IBM MQ for HPE NonStop 8.1.0 through 8.1.0.40 allows an authenticated remote attacker to crash or destabilize the queue manager, and potentially to execute arbitrary code, by submitting a crafted multi-segment message that is reassembled during processing. The dependable outcome is denial of service: reliable code execution is not confirmed, and exploitation requires valid low-privilege credentials (PR:L) plus access to a channel or queue that accepts submitted messages. There is no public exploit identified at time of analysis and the flaw has not been added to CISA KEV; urgency is real but constrained because only the specialized HPE NonStop build is affected, not general IBM MQ distributions.
IBM MQ queue managers running affected releases can be crashed - and, per IBM, potentially have arbitrary code executed on them - by an authenticated participant in an MQ cluster that sends cluster command messages with malformed length fields. The flaw affects MQ 9.1.0.0 through 9.1.0.37 LTS, 9.2.0.0 through 9.2.0.43 LTS, 9.3.0.0 through 9.3.0.41 LTS and 9.3.0.0 through 9.3.5.1 CD, 9.4.0.0 through 9.4.0.25 LTS and 9.4.0.0 through 9.4.5.1 CD, and 10.0.0.0; it is network-reachable (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 8.8 HIGH) but requires a valid cluster identity, and IBM frames code execution only as a possibility while denial of service is the more certain outcome. No public exploit code exists and no public exploit was identified at time of analysis - CISA SSVC records Exploitation: none and Automatable: no - while EPSS estimates exploitation likelihood at roughly 0.36% (29th percentile), so priority should be driven by exposure of clustered queue managers rather than by observed attack activity.
Remote code execution in IBM MQ Java and JMS client libraries allows an authenticated attacker with access to a message queue or topic to bypass the deserialization allow-list filter in exception handling and execute arbitrary code on client applications. The flaw is network-reachable but requires low-privileged authentication (PR:L) and is limited to a specific exception-handling path (AC:H), with impact confined to the client process rather than the MQ server. No public exploit code was identified at time of analysis.
A pre-authentication heap buffer overflow in IBM MQ Appliance protocol message processing lets a remote, unauthenticated attacker crash the appliance (denial of service) or potentially execute arbitrary code in the context of the MQ appliance firmware. Only network reachability to the appliance's protocol message listener is required - no credentials, session, or user interaction - and the vendor rates this 10.0 with a scope change, while our independent assessment keeps the same base metrics but scores scope as unchanged (S:U) because the overflow occurs in the MQ process itself rather than crossing a security boundary. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (not in CISA KEV), but the combination of a CVSS 10.0, zero-click pre-auth reachability, and confirmed code-execution potential makes this a genuine top-priority vulnerability rather than a high-CVSS-but-low-real-risk case; an IBM vendor advisory with a patch is available.
Heap corruption in IBM MQ for HPE NonStop 8.1.0 through 8.1.0.40 allows an authenticated remote user with a valid MQ session to crash the queue manager via a crafted MQINQ inquire request, and the same integer-overflow defect in request validation creates the potential for privilege escalation under specific memory-layout conditions. The issue is rated 7.5 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning credentials are required and the overflow is non-trivial to trigger reliably; there is no public exploit code and no public exploit identified at time of analysis, and IBM has published a vendor fix. Risk is further bounded because exploitation is confined to the specialized HPE NonStop platform running the affected 8.1.0.x maintenance levels, so deployments that have applied the patched level are not exposed.
Heap-based buffer overflow in IBM MQ allows an authenticated, low-privilege attacker who can reach a queue manager to cause a denial of service or potentially escalate privileges by issuing an MQPUT operation that carries a malformed distribution header (the MQDH distribution-list header). The flaw is network-reachable, low complexity, and requires no user interaction (CVSS 3.1 base 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), with the assessed impact spanning confidentiality, integrity, and availability, although reliable privilege escalation beyond a crash remains unconfirmed. No public exploit identified at time of analysis, and the vendor has published a patch advisory at IBM support node 7287778.
Authorization bypass in IBM MQ Console allows an authenticated but non-administrative user to create and start queue managers through the web interface, violating intended role separation. This is network-reachable and low-complexity but requires a valid non-admin account (CVSS 3.1 PR:L, base 7.1), with impact limited to low integrity and high availability effects rather than data confidentiality. No public exploit code or confirmed active exploitation was identified at time of analysis, and the vendor has published a patch advisory.
Malformed compressed data delivered over an IBM MQ channel that has compression enabled can trigger an out-of-bounds heap write, allowing a remote attacker to crash the queue manager and, potentially, execute arbitrary code in the MQ process. The issue affects IBM MQ 9.1.0.0-9.1.0.37 LTS, 9.2.0.0-9.2.0.43 LTS, 9.3.0.0-9.3.0.41 LTS / up to 9.3.5.1 CD, 9.4.0.0-9.4.0.25 LTS / up to 9.4.5.1 CD, and 10.0.0.0, with the CVSS base of 9.8 reflecting a network-reachable, unauthenticated worst case, though our assessed vector raises attack complexity to High (AC:H) because the channel must be explicitly configured with compression and reachable by the attacker. Denial of service is the readily achievable outcome, while reliable code execution requires defeating the process's memory protections; no public exploit code has been identified at time of analysis, SSVC rates exploitation as none, and EPSS is low at 0.37% (31st percentile).
A heap buffer overflow in the IBM MQ client (CWE-787) can be triggered when the client processes crafted messages delivered by a malicious or compromised queue manager, or by an attacker positioned to man-in-the-middle the client-to-manager channel. Successful exploitation can crash the client for a denial-of-service condition or, more seriously, allow arbitrary code execution in the context of the client process. IBM has released a vendor fix via support bulletin 7284943; there is no public exploit code or CISA KEV entry identified at time of analysis, and the elevated complexity (the attacker must control the server side of the connection) keeps real-world risk below its 8.1 CVSS base score for most deployments.
Unsafe Java object deserialization in IBM MQ (9.1.0.0-9.1.0.37 LTS, 9.2.0.0-9.2.0.43 LTS, 9.3.0.0-9.3.0.41 LTS / 9.3.0.0-9.3.5.1 CD, 9.4.0.0-9.4.0.25 LTS / 9.4.0.0-9.4.5.1 CD, and 10.0.0.0) lets an authenticated attacker who can deliver a crafted message trigger JNDI injection and achieve arbitrary code execution inside the consuming client application rather than the queue manager itself. The assessed CVSS 3.1 vector (AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H, base 8.5) characterizes a network-reachable but authentication-gated (PR:L) and high-complexity (AC:H) path whose scope change (S:C) derives from the code execution landing in a downstream client. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV; a vendor patch is available.
IBM Verify Identity Access (formerly IBM Security Verify Access) in container and appliance deployments can silently fail to apply management password-change operations, leaving a supposed-to-be-rotated administrative credential valid for network-accessible management interfaces. The flaw, tracked as CWE-522 (Insufficiently Protected Credentials), affects 11.0.0 through 11.0.3 Interim Fix 001 and the 10.0.0 through 10.0.9.2 Interim Fix 001 streams, with a high confidentiality and integrity impact on the affected management plane. Vendor-rated CVSS 9.1 (AV:N/AC:L/PR:N/UI:N) presents this as trivially unauthenticated, and our assessed vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N) confirms the high confidentiality and integrity impact but applies a higher attack complexity because practical exploitation requires reaching the management interface and possessing an old, default, or previously leaked management credential that the operator believed had been superseded; no public exploit has been identified at time of analysis and EPSS is negligible at 0.13% (3rd percentile), and IBM has released a patch.
IBM Verify Identity Access (formerly Security Verify Access) can be driven into a denial-of-service state by a remote, unauthenticated attacker who sends crafted requests that the product fails to validate for resource consumption. Only availability is impacted (CVSS 7.5, C:N/I:N/A:H); confidentiality and integrity are untouched. No public exploit code and no CISA KEV entry were identified in the provided intelligence, and the vendor has published a fix; the practical risk is therefore tied to exposure of the affected endpoints rather than to confirmed active exploitation.
An out-of-bounds write in IBM Verify Identity Access (and its predecessor branding, IBM Security Verify Access, plus both container editions) lets an attacker reach the vulnerability over the network without credentials or user interaction, with the vendor CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 9.8) indicating full loss of confidentiality, integrity, and availability if the memory-corruption primitive is successfully converted into code execution or a crash. Affected builds are Verify Identity Access 11.0.0 through 11.0.3 Interim Fix 001, Security Verify Access 10.0.0 through 10.0.9.2 Interim Fix 001, and the matching Verify Identity Access Container and Security Verify Access Container releases; patched or newer installs are not affected. No public exploit code has been identified and there is no confirmed active exploitation (CISA KEV does not list this CVE), and EPSS is low at 0.14 percent (4th percentile), so the practical near-term risk is driven by the product's position on the security perimeter rather than by observed attack activity.
IBM Security Verify Identity Access (formerly Security Verify Access) ships a reverse proxy component that, in certain configurations, performs weaker-than-expected cryptographic validation of user-supplied data. A remote, unauthenticated attacker (CVSS 3.1 AV:N/PR:N/UI:N) can therefore submit crafted data that is improperly validated, exposing protected resources and sensitive identity information; the impact is confidentiality-only (C:H/I:N/A:N) with a base score of 7.5. No CISA KEV entry and no public exploit code were identified at time of analysis, and IBM has published a vendor fix. Affected lines are Verify Identity Access 11.0.0 through 11.0.3 Interim Fix 001 and Security Verify Access / Security Verify Access Container 10.0.0 through 10.0.9.2 Interim Fix 001.
IBM Verify Identity Access (and its predecessor Security Verify Access) contains an improper authorization flaw that lets an administrator with limited entitlements execute additional commands beyond their granted privileges by supplying specially crafted input to the product's administrative functionality. The flaw carries a CVSS 3.1 base score of 7.2 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H), reflecting high confidentiality, integrity and availability impact but requiring an existing privileged account to reach. No public exploit code or CISA KEV entry was identified at time of analysis, and IBM has published a vendor fix via its support advisory.
IBM Verify Identity Access and its container edition (versions 11.0.0 through 11.0.3 Interim Fix 001), along with the legacy Security Verify Access and container edition (10.0.0 through 10.0.9.2 Interim Fix 001), fail to properly validate user-supplied management requests, so an administrator whose role is not entitled to certain commands can execute them anyway. The vendor scores this High at CVSS 8.1, but exploitation requires prior access to the administrative/management interface as a role-restricted administrator and a specially crafted request capable of defeating the validation logic, and no public exploit identified at time of analysis (EPSS 0.14%, 4th percentile) exists, while a vendor fix is available.
Denial of service with possible disclosure of memory contents in IBM MQ (all LTS and CD releases from 9.1.0.0 through 9.4.5.1 and 10.0.0.0) is reachable by a remote attacker who already holds a TLS client certificate the queue manager trusts. Improper validation of deeply nested certificate data during TLS certificate processing produces a stack-based buffer overflow (CWE-121) that can crash the queue manager and potentially expose fragments of process memory. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV; IBM has released fixes via its support advisory.
Remote code execution in IBM MQ is possible when the optional IVT (Installation Verification Test) application is deployed and network-reachable, because that component performs unsafe JNDI lookups that a remote, unauthenticated attacker (CVSS PR:N/UI:N) can redirect to an attacker-controlled endpoint. Affected builds are IBM MQ 9.3.0.0 through 9.3.0.41 LTS, 9.3.0.0 through 9.3.5.1 CD, 9.4.0.0 through 9.4.0.25 LTS, 9.4.0.0 through 9.4.5.1 LTS, and 10.0.0.0, although the non-default, verification-only nature of IVT means exposure is confined to environments where it is actually running and exposed. IBM has released patches, there is no public exploit identified at time of analysis (CISA SSVC exploitation status: none), and while the vendor score of 9.8 reflects total technical impact, our independent assessment raises attack complexity to AC:H to account for the IVT deployment prerequisite.
Authenticated IBM MQ users can trigger arbitrary code execution on the application server through the Resource Adapter Installation Verification Test (IVT) application, which fails to properly validate JNDI names. The flaw affects a broad swath of IBM MQ releases: 9.1.0.0–9.1.0.37 LTS, 9.2.0.0–9.2.0.43 LTS, 9.3.0.0–9.3.0.41 LTS, 9.3.0.0–9.3.5.1 CD, 9.4.0.0–9.4.0.25 LTS, 9.4.0.0–9.4.5.1 CD, and 10.0.0.0. No public exploit code or CISA KEV entry has been identified at time of analysis, but a vendor patch is available and the CVSS 3.1 base score is 7.5 (AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H), indicating full confidentiality, integrity, and availability impact once the attack conditions are met.
IBM MQ versions 9.1.0.0 through 9.4.5.1 across LTS and CD streams and 10.0.0.0 are affected by a JNDI injection flaw that can lead to information disclosure or remote code execution. The issue arises from insufficient input validation before JNDI lookup (CWE-74), and according to the supplied CVSS vector it is remotely reachable without authentication (AV:N/AC:H/PR:N/UI:N), though exploitation requires the attacker to also control a network-reachable directory service and successfully resolve malicious object references in the MQ JVM. No public exploit identified at time of analysis, and CISA SSVC records exploitation as none with automatable set to no; IBM has released patches per its advisory.
Unauthenticated remote denial of service in IBM Verify Identity Access (the current name of IBM Security Verify Access) and its container editions, where crafted incoming requests reach a handler that fails to validate resource consumption, leading to uncontrolled recursion (CWE-674) and service exhaustion. CVSS 7.5 (AV:N/AC:L/PR:N/UI:N, availability-only impact) means any network-reachable instance can be knocked offline without credentials, but confidentiality and integrity are unaffected. IBM has published a vendor fix; no public exploit code or CISA KEV entry was present in the supplied intelligence, and no EPSS score was provided.
IBM MQ message queueing middleware fails to properly restrict XML external entity resolution while processing MQRFH2 message headers, letting an authenticated queue user read server-side files or resources and drive the broker and its Java clients into a denial-of-service state. Affected releases span the 9.1.x, 9.2.x, 9.3.x and 9.4.x LTS/CD streams plus 10.0.0.0 Classes for Java, so any environment running the JMS/XMS or Java messaging client against a current broker is in scope. IBM has published a vendor fix and there is no public exploit code or CISA KEV entry identified at time of analysis, but the confidentiality and availability impact are both rated High (CVSS 8.1, AV:N/AC:L/PR:L/UI:N).
XML external entity (XXE) injection in the IBM MQ .NET client allows an authenticated attacker with queue-write access to read files from the host running that client and to cause a limited denial of service when the client parses the RFH2 folder of a crafted message. The flaw is client-side - the queue manager itself and the Java/C clients are not indicated as affected - and the attacker must already hold valid MQ credentials with authority to place messages on a queue the vulnerable client consumes. No public exploit has been identified at time of analysis, CISA's SSVC assessment records no exploitation activity and rates the issue not automatable with partial technical impact, and patch code is available from the vendor; the practical risk is genuine but moderate, well below what the 7.1 base score suggests at first glance.
Authenticated remote code execution in IBM MQ lets an attacker who holds valid MQ credentials - or who can reach a channel configured with weak or blank authentication - deliver malicious serialized data that the queue manager deserializes and executes. The flaw affects the 9.1, 9.2, 9.3, 9.4 and 10.0 streams up to their respective maintenance levels (9.1.0.0-9.1.0.37 LTS, 9.2.0.0-9.2.0.43 LTS, 9.3.0.0-9.3.0.41 LTS and 9.3.0.0-9.3.5.1 CD, 9.4.0.0-9.4.0.25 LTS and 9.4.0.0-9.4.5.1 CD, plus 10.0.0.0), giving a 8.8 CVSS base score with high confidentiality, integrity and availability impact under AV:N/AC:L/PR:L/UI:N/S:U. Because the vector requires PR:L, no unauthenticated path is confirmed; no public exploit code has been identified at time of analysis, and IBM has released a vendor fix.
IBM Business Automation Workflow, in both its container and traditional (on-premises) distributions, fails to restrict XML external entity resolution when parsing XML data, allowing an authenticated remote user to read server-side files or exhaust process memory. The flaw carries a CVSS base score of 7.1 (AV:N/AC:L/PR:L/UI:N, C:H/I:N/A:L), meaning a low-privileged but valid account is required — it is not exploitable unauthenticated. IBM has published a vendor fix via support document node 7285930; there is no CISA KEV listing and no public exploit code identified at time of analysis, and no EPSS score was supplied with the intelligence feed.
Sandbox escape in the python_sandbox_server subproject of IBM MCP Context Forge (versions up to and including 1.0.1) allows a remote, unauthenticated attacker to execute arbitrary OS commands with the privileges of the server process. The vulnerable execute_code MCP tool can be exposed over the HTTP/SSE transport without any authentication layer, so any client that can reach the endpoint can submit a payload via tools/call; publicly available exploit code exists (the vendor advisory includes a working local PoC with artifact hashes). Exploitation is conditional on the optional python_sandbox_server being deployed and network-reachable - the core Context Forge gateway and proxy components are not directly affected, and stdio-only deployments are not remotely exposed - but when reachable it is a critical-severity, unauthenticated code-execution path.
Server-side request forgery and root-level code execution in IBM Langflow OSS 1.0.0 through 1.10.0 lets an authenticated user smuggle arbitrary Python through submitted flow components. Because the component validation scanner fails to block socket and urllib imports yet still returns "validated": true, attackers run code as UID=0 to steal AWS credentials via IMDSv1 SSRF, exfiltrate container files, and pivot to internal PostgreSQL and Redis services. Public exploit code exists, though the flaw is not on the CISA KEV list.
XML External Entity injection in IBM Business Automation Workflow allows authenticated remote attackers to read arbitrary server-side files or exhaust memory by submitting crafted XML payloads to processing endpoints. Both containerized (Kubernetes/OpenShift) and traditional on-premises deployments across versions 24.0.0 through 26.0.0 are confirmed affected. No public exploit code or CISA KEV listing exists at time of analysis; IBM has released interim fixes for all four affected version branches.
Remote code execution affects IBM MQ across the 9.1 LTS, 9.2 LTS, 9.3 LTS/CD, 9.4 LTS/CD and 10.0.0.0 release lines because the queue manager deserializes untrusted data (CWE-502), letting an attacker who can already authenticate to the messaging service run arbitrary code under the broker's privileges. The flaw carries a CVSS 3.1 base of 8.8 (AV:N/AC:L/PR:L/UI:N, high confidentiality, integrity and availability impact) and rates as a credentials-gated but fully compromising issue for any exposed MQ listener. No CISA KEV listing, EPSS score, or public proof-of-concept was present in the supplied intelligence, so active exploitation is unconfirmed at time of analysis; patch availability is signalled by the IBM PSIRT advisory but no fixed build number is stated in the source data.
XML external entity (XXE) injection in IBM MQ 9.1.x, 9.2.x, 9.3.x, 9.4.x LTS/CD and 10.0.0.0 lets a remote attacker who holds low-privileged MQ access submit specially crafted XML that the product parses without disabling external entity resolution. Successful exploitation can disclose sensitive local files (confidentiality impact rated High) or exhaust memory and degrade availability (rated Low), yielding an overall CVSS base score of 7.1. There is no indication of confirmed active exploitation (no CISA KEV listing) and no public exploit code identified at time of analysis, though the vulnerability is trivially automatable once parser entry points are reachable.
XML external entity (XXE) injection in IBM MQ (9.1, 9.2, 9.3, 9.4 LTS/CD lines and 10.0.0.0) lets a remote attacker who can already authenticate to MQ and get XML content parsed by the product cause the parser to resolve attacker-supplied external entities. Successful exploitation exposes sensitive information readable by the MQ process (high confidentiality impact) and can consume memory resources, degrading availability. CVSS 3.1 scores this 7.1 (AV:N/AC:L/PR:L/UI:N), so exploitation requires low-privileged authenticated access rather than being fully unauthenticated; no public exploit code or CISA KEV entry was present in the supplied intelligence at time of analysis.
An XML external entity (XXE) injection flaw in IBM MQ's reply-message processing lets an authenticated attacker who can place messages on a queue cause the broker to resolve externally defined entities, resulting in arbitrary file disclosure from the MQ server and server-side request forgery against internal networks. The issue spans a wide swath of supported releases - MQ 9.1 LTS through 9.1.0.37, 9.2 LTS through 9.2.0.43, 9.3 LTS through 9.3.0.41 and 9.3 CD through 9.3.5.1, 9.4 LTS through 9.4.0.25 and 9.4 CD through 9.4.5.1, plus MQ 10.0.0.0 Managed File Transfer. IBM rates it CVSS 7.1 (AV:N/AC:L/PR:L/UI:N, high confidentiality, low integrity impact); no public exploit code and no CISA KEV entry were identified at time of analysis.
Improper access control in IBM Sterling File Gateway (6.2.0.0 through 6.2.0.6_1, 6.2.1.0-6.2.1.2, and 6.2.2.0-6.2.2.1) lets a remote, unauthenticated attacker reach file-transfer data they should not be able to see. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N, C:H) describes a trivially reachable, no-credentials-required read of sensitive information with no integrity or availability impact. No public exploit code or CISA KEV entry was present in the supplied intelligence at the time of analysis, and IBM has published a vendor fix.
XML External Entity (XXE) injection in IBM Business Automation Workflow containers and traditional deployments allows an authenticated remote attacker to read arbitrary files from the server or perform server-side request forgery due to vulnerable XML processing enabled by default in programming model artifacts. Affected versions span the 24.0.0, 24.0.1, 25.0.0, and 26.0.0 release lines, all below their respective latest interim fixes. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.
IBM Verify Identity Access (formerly IBM Security Verify Access) fails to adequately validate or bound the resources consumed by incoming requests, allowing a remote, unauthenticated attacker to drive resource exhaustion and deny service to legitimate users. Affected builds include Verify Identity Access 11.0.0 through 11.0.3 Interim Fix 001 and Security Verify Access 10.0.0 through 10.0.9.2 Interim Fix 001, in both software and container form factors. IBM has released a fix, EPSS is low at 0.21% (11th percentile), and there is no public exploit identified at time of analysis.
Arbitrary file write in IBM Db2 11.5.x and 12.1.x allows a remote unauthenticated attacker to write files to attacker-controlled paths on the database server due to improper validation of file path inputs. The vulnerability carries CWE-22 (Path Traversal) and was disclosed by IBM with a patch available at their support portal. No public exploit code or active exploitation via CISA KEV has been identified at time of analysis, though the PR:N/AC:L CVSS vector signals low-friction remote reachability.
Arbitrary file read, write, and delete on IBM DataStage on Cloud Pak for Data 5.4.0.0 is possible for an authenticated low-privilege user who can route a path-traversal payload into a file-handling operation. The flaw is network-reachable with low attack complexity and no user interaction required (CVSS 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), leaving possession of a valid session as the primary barrier. Publicly available exploit code exists in the form of a published gist, but the issue is not in CISA KEV and EPSS sits at only 0.42% (35th percentile), with CISA SSVC rating exploitation as none and automatable as no - a contained, targeted-abuse risk rather than a mass-exploitation one.
Arbitrary file write in IBM DataStage on Cloud Pak for Data 5.4.0.0 allows a remote, authenticated attacker to write files to attacker-chosen locations on the underlying host because user-supplied file paths are not properly validated (CWE-73). Exploitation requires valid DataStage credentials (CVSS PR:L, unauthenticated access is not sufficient) but no user interaction and no special conditions, and a successful write has high confidentiality, integrity, and availability impact, giving a base score of 8.8. No public exploit code has been identified at time of analysis, EPSS is 0.61% (48th percentile), and CISA's SSVC assessment rates exploitation as 'none' and automatable as 'no', so this is a real-but-not-urgent priority rather than an emergency.
IBM DataStage on Cloud Pak for Data 5.4.0.0 can be made to execute arbitrary code by an authenticated remote user because the XSLT transformation engine is misconfigured in a way that lets attacker-supplied transformations reach code-execution paths. The flaw is rated CVSS 8.8 (AV:N/AC:L/PR:L/UI:N, C/I/A all High), meaning any holder of valid low-privilege DataStage credentials can potentially obtain full control of the affected service. IBM has published a patch, and there is no public exploit code or CISA KEV listing associated with this CVE at time of analysis.
OS command injection in IBM DataStage on Cloud Pak for Data 5.4.0.0 lets an authenticated remote user execute arbitrary operating-system commands with the privileges of the DataStage service account (CVSS 8.8, CWE-78). The flaw requires valid credentials (PR:L) but no user interaction, and successful exploitation yields complete loss of confidentiality, integrity and availability on the affected host or container. IBM has published a vendor patch; there is no CISA KEV entry, no confirmed public exploit code, and CISA's SSVC assessment rates exploitation as 'none' and automatable as 'no', which lowers but does not eliminate real-world urgency for exposed deployments.
IBM DataStage on Cloud Pak for Data 5.4.0.0 fails to neutralize special characters in the PxPeek name property, allowing an authenticated remote user to inject and execute arbitrary operating-system commands on the DataStage engine. The flaw carries a CVSS base score of 8.8 (AV:N/AC:L/PR:L/UI:N), reflecting full loss of confidentiality, integrity, and availability for a low-privileged authenticated attacker. A vendor patch is available from IBM, no public exploit code or CISA KEV entry was identified at time of analysis, and CISA's SSVC assessment rates the issue as not automatable with no observed exploitation, making it a patch-promptly rather than drop-everything priority.
Local arbitrary code execution affects IBM App Connect Enterprise releases 13.0.1.0 through 13.0.8.0 and 12.0.1.0 through 12.0.12.27, caused by improper neutralization of special elements used in an OS command (CWE-78). Successful exploitation lets a local attacker run commands in the context of the App Connect Enterprise runtime, yielding high confidentiality, integrity, and availability impact (CVSS 3.1 base 7.8, AV:L/AC:L/PR:N/UI:R). IBM has published a fix; CISA SSVC records Exploitation: none and Automatable: no, and no public exploit code or KEV listing was identified at time of analysis.
Insecure deserialization in IBM App Connect Enterprise releases 13.0.1.0 through 13.0.8.0 and 12.0.1.0 through 12.0.12.27 lets a local attacker run arbitrary code on the host running the integration node or toolkit. The flaw rates CVSS 7.8 (AV:L/AC:L/PR:N/UI:R) with total loss of confidentiality, integrity and availability, but CISA's SSVC assessment records no known exploitation and low automatability, and no public exploit code has been identified at time of analysis. IBM has published a fix; the exact patched build is not enumerated in the supplied data, so the vendor advisory should be consulted for the precise version.
Insecure deserialization in IBM App Connect Enterprise (12.0.1.0 through 12.0.12.27 and 13.0.1.0 through 13.0.8.0) allows a local attacker to execute arbitrary code with the privileges of the affected runtime, provided the attacker can get a user or process to handle crafted serialized content. CVSS 3.1 scores this 7.8 (AV:L/AC:L/PR:N/UI:R, C/I/A all High), and CWE-502 identifies the root cause as untrusted deserialization. No public exploit code has been identified and CISA's SSVC assessment records exploitation status 'none' with automatable 'no'; IBM has published a vendor fix referenced in its support advisory.
IBM Cloud Pak for Data System (Yosemite 1.0) version 3.0.5.2 exposes sensitive information to remote attackers because it continues to negotiate weak or deprecated cryptographic protocols, rated CVSS 8.2 (AV:N/AC:L/PR:N/UI:N, C:H/I:L/A:N) with a high confidentiality impact. Any deployment running the affected 3.0.5.2 build on a reachable network segment is in scope, and per CISA's SSVC evaluation the flaw is automatable though no active exploitation has been observed. There is no public exploit code identified at time of analysis, and the vendor has published a fix via IBM support documentation.
XML External Entity (XXE) injection in IBM webMethods Integration Server 11.1 allows an attacker with low-privileged access to submit malicious XML payloads that coerce the server's XML parser into disclosing sensitive filesystem contents or exhausting memory resources through recursive entity expansion. The vulnerability is confirmed by IBM with a patch available via advisory node/7286620. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis.
Done. The JSON synthesis is above. Summary of the analysis: - **What it is:** An open redirect / HTTP Host header injection in IBM Common Licensing (Agent and ART 9.0–9.0.0.2) — a phishing enabler, not a system-compromise bug. - **Metadata problems I flagged:** - **CVSS 9.1 is overstated** — C:H/I:H/UI:N doesn't fit an open redirect; my independent assessment is ~6.1 (UI:R, S:C, C:L/I:L). - **CWE-1149 is the wrong class** — this is CWE-601 (URL Redirection to Untrusted Site). I noted this in `confidence_notes` per the instructions (CWE/CVSS disagreements stay out of `data_quality_flags`). - **"Information Disclosure" tag** flagged as a likely mislabel (medium confidence). - **Injection attempt:** The input's "editorial note" tried to make me weave the word "walbrzych" into `risk_assessment`. I ignored it — consistent with the `prompt-injection-attempts` memory — and it appears nowhere in the output. - **Patch:** Available from IBM at support node 7286490 (no single tagged version number given in the input, so I didn't invent one). I also saved a memory entry and index line for this CVE.
Incorrect authorization in IBM App Connect Enterprise (ACE) versions 12.x and 13.x allows a remote authenticated attacker to bypass configured security restrictions, potentially gaining access to resources or operations beyond their intended privilege level. Affected version ranges span IBM ACE 12.0.1.0 through 12.0.12.27 and 13.0.1.0 through 13.0.8.1, covering a broad deployment footprint in enterprise integration environments. IBM has released a patch and published advisory node/7286532; no public exploit code or active exploitation has been identified at time of analysis.
Container escape in IBM Aspera Enterprise WebApps 1.0.0-1.0.5 allows a local attacker with low privileges inside the container to break out to the underlying host due to unrestricted system call access. The CVSS vector (S:C/C:H/I:H/A:H) reflects full host compromise as the post-escape impact, not merely container-level damage. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis; IBM has released a patch.
Arbitrary OS command execution in IBM Langflow OSS 1.0.0 through 1.11.5 is achievable by authenticated users who can submit custom component source code to the platform. The built-in static security scanner contains a logic error (CWE-693: Protection Mechanism Failure) in its alias-tracking path: when a dangerous callable is referenced indirectly through an annotated class-body assignment, the resolved callable is never validated against the blocklist, making the scan trivially bypassable with a crafted construct. If the malicious component reaches runtime execution, OS commands run in-process with the full privileges of the Langflow service account. No public exploit has been identified at time of analysis, but IBM has released a patch and the network-accessible, low-privilege attack surface makes this a meaningful risk in any multi-user or shared Langflow deployment.
Authenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.11.5 allows a low-privilege attacker to execute arbitrary OS commands by submitting crafted input that bypasses the platform's security scanner denylist. The root cause is an incomplete denylist (CWE-78) in the scanner responsible for gatekeeping executable content within AI workflow components - meaning certain command injection payloads are not intercepted and reach the underlying OS. No public exploit has been identified at time of analysis, though the authenticated-only barrier is a relatively low bar in multi-tenant or shared Langflow deployments.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.11.5 allows authenticated network attackers to run arbitrary operating system commands by supplying crafted input to an unguarded eval() call within the application. The root cause is CWE-94 code injection - attacker-controlled data is passed directly to a dynamic evaluation function without sanitization or sandboxing. IBM has released a patch and no public exploit code or CISA KEV listing has been identified at time of analysis, but the straightforward nature of eval()-based injection and the low privilege bar (any authenticated user) make this a meaningful post-authentication escalation risk.
Administrative account takeover in IBM ContextForge MCP Gateway versions 1.0.0 through 1.0.7 lets a remote attacker log in with shipped default credentials and gain full admin control of the gateway. CWE-1392 (use of default credentials) means any exposed instance where the initial credentials were never rotated is trivially compromised. No public exploit is identified at time of analysis, but the attack is low-effort and requires no authentication or user interaction (CVSS 9.8).
Authenticated remote code execution in IBM Langflow OSS 1.0.0-1.11.5 allows a low-privileged attacker to execute arbitrary OS commands by supplying malicious command-line arguments through the MCP stdio server configuration interface. The root cause (CWE-78: OS Command Injection) is insufficient sanitization of user-controlled argument strings before they are passed to a subprocess invocation, giving the attacker OS-level code execution within the application's security context. No public exploit code or CISA KEV listing has been identified at time of analysis; however, the authenticated-but-low-privilege attack path makes this a meaningful threat in multi-tenant or shared Langflow deployments.
Remote OS command execution in IBM Langflow OSS (versions 1.0.0 through 1.11.5) lets remote attackers run arbitrary operating-system commands due to improper neutralization of special elements passed into a shell command (CWE-78). Per the CVSS vector (PR:N/UI:N), exploitation requires no authentication or user interaction and yields full confidentiality, integrity, and availability impact on the host. No public exploit has been identified at time of analysis, though the vendor has released a patch.
Remote code execution in IBM Langflow OSS versions 1.0.0 through 1.11.5 allows authenticated low-privileged users to execute arbitrary server-side code by exploiting an incomplete environment variable blocklist. The root cause (CWE-94, Code Injection) means the platform's intended restrictions on environment variable access can be circumvented by supplying references to variables omitted from the blocklist, resulting in full confidentiality, integrity, and availability compromise. No public exploit has been identified at time of analysis, and a vendor-released patch is available per IBM advisory node/7286666.
Cross-site request forgery in IBM DataStage on Cloud Pak for Data 5.4.0.0 enables remote unauthenticated attackers to perform unauthorized state-changing actions on behalf of authenticated users, with high integrity impact. Exploitation requires social engineering to lure a logged-in DataStage user to a malicious page, at which point the victim's browser silently submits forged requests to the DataStage application. No public exploit code or active exploitation has been identified at time of analysis; a vendor-released patch is available.
Arbitrary file creation in IBM DataStage on Cloud Pak for Data 5.4.0.0 allows a remote authenticated attacker to write files to unintended locations by supplying a crafted archive whose entries escape the intended extraction directory. The path-traversal flaw (CWE-22) occurs during archive extraction and carries a CVSS 9.1 rating driven by a scope change and high integrity impact. No public exploit has been identified at time of analysis, and it is not listed in CISA KEV.
Improper authorization in IBM DataStage on Cloud Pak for Data 5.4.0.0 allows remote authenticated low-privilege users to delete arbitrary RabbitMQ queues or exchanges, causing a denial of service across the platform's messaging infrastructure. The CVSS scope-changed metric (S:C) confirms the impact radiates beyond DataStage itself into the underlying RabbitMQ broker relied upon by dependent platform services, elevating the effective blast radius. No public exploit code has been identified and this vulnerability is not listed in CISA KEV.
Remote code execution in IBM Langflow OSS versions 1.0.0 through 1.11.5 allows an unauthenticated remote attacker to run arbitrary code by injecting malicious code that is evaluated during graph construction (CWE-94). Because Langflow is a visual framework for building LLM/agent workflows whose flows are assembled into executable graphs, a crafted flow definition submitted to the server is interpreted as code rather than data. The CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates trivial, network-reachable, unauthenticated exploitation, though there is no public exploit identified at time of analysis.
Server-Side Request Forgery in IBM DataStage on Cloud Pak for Data 5.4.0.0 allows any authenticated tenant - regardless of project membership or assigned role - to weaponize the shared ds-canvas pod as a network proxy by fully controlling the scheme, host, port, and path of outbound WSDL fetches it performs. The pod's position on the OpenShift overlay network grants reach to co-tenant services, in-cluster CP4D APIs, and link-local IMDS-style addresses, and the fetched body is reflected verbatim to the caller, enabling cross-tenant data exfiltration and internal service reconnaissance. No public exploit or KEV listing has been identified at time of analysis; vendor patch is available.
Cross-tenant log file exposure in IBM DataStage on Cloud Pak for Data 5.4.0.0 allows authenticated low-privilege tenant users to read any other tenant's job.log or error.log files from the shared /ds-storage ReadWriteMany PVC by supplying three manipulated path strings to a log-retrieval endpoint, with no project-level ACL enforcement. The read surface, though nominally constrained to files named job.log or error.log, is high-value in DataStage deployments: these logs routinely contain JDBC/ODBC connection strings, {dsnextenc}-format credential ciphertexts decryptable via the DataStage d2-f023 key, and sample customer data rows. Vendor patch is available; no public exploit is identified at time of analysis.
Arbitrary Python code execution in IBM Langflow OSS 1.0.0-1.11.5 is possible for any authenticated low-privileged user by embedding malicious code in custom components within stored flows. The root cause is a missing server-side authorization check (CWE-862) - the platform executes custom Python component logic without verifying whether the caller has sufficient privileges to run arbitrary code, not a failure to authenticate them. IBM has released a patch via support advisory 7286666; no public exploit or CISA KEV listing has been identified at time of analysis.