IBM
Monthly
Unauthenticated path traversal in IBM Guardium Data Protection 12.0, 12.1, and 12.2 can be leveraged by remote attackers to execute arbitrary code on the affected deployment, producing a vendor CVSS 3.1 base score of 9.8 from the vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Per that vector the flaw requires no authentication, no user interaction, and no non-default configuration, so the only practical barrier is network reachability of the exposed Guardium interface; because the product is normally deployed inside segmented enterprise networks, internet-wide exposure is expected to be limited. There is no public exploit identified at time of analysis and no confirmed active exploitation, but the worst-case skill and access profile place this in the urgent patching tier for any instance reachable from untrusted networks; the specific traversal entry point and the path from traversal to code execution are not detailed in the available advisory data and should be confirmed against IBM support node 7291674.
Unauthenticated SQL injection in IBM Guardium Data Protection 12.0, 12.1, and 12.2 allows a remote attacker to execute unauthorized SQL statements against the appliance, with the vendor-assessed 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 compromise of confidentiality, integrity, and availability of the affected component with no privileges or user interaction required. The vulnerable feature or endpoint is not publicly disclosed, so defenders cannot pin down a specific setting to harden, but the practical gating factor is reachability: Guardium is a data-security management appliance that normally sits on an internal or management network segment rather than the public internet. No public exploit code has been identified at time of analysis and there is no CISA KEV listing, but a vendor patch is available and should be treated as high priority because of the 9.8 severity and the sensitivity of the data Guardium manages.
Remote code execution in IBM Guardium Data Protection 12.0, 12.1, and 12.2 is enabled by a buffer overflow that an unauthenticated network attacker can trigger without user interaction, consistent with the assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H and a base score of 9.8, giving total loss of confidentiality, integrity, and availability on a successful exploit. No public exploit code has been identified at time of analysis, CISA's SSVC assessment records no observed exploitation with non-automatable attack steps, and EPSS places exploitation likelihood at 0.37% (29th percentile), so signals are mixed and point to a credible-but-not-yet-urgent priority. The practical limiting factor is network reachability: Guardium is typically deployed as an internal database-activity-monitoring appliance, so an attacker generally needs a foothold on, or routing into, the management or database-monitoring network rather than open internet access.
IBM Guardium Data Protection 12.1 and 12.2.2 contain a path traversal flaw (CWE-22) that lets a remote, unauthenticated attacker delete arbitrary files on the appliance by supplying traversal-laden input to an affected file-handling function, giving a high-integrity and availability impact with no confidentiality exposure (CVSS 3.1: 9.1, AV:N/AC:L/PR:N/UI:N/C:N/I:H/A:H). No public exploit code has been identified at time of analysis, EPSS is low at 0.36% (28th percentile), and CISA's SSVC decision framework rates exploitation as 'none' with a total technical impact, so this reads as a serious but not emergency-priority issue. Practical risk is bounded by reachability: Guardium is a management-plane appliance normally confined to privileged database and security administrators behind the enterprise perimeter, which narrows the realistic attacker population despite the network-vector rating.
SQL injection in IBM Guardium Data Protection 12.0, 12.1, and 12.2 lets remote unauthenticated attackers who can reach the product's network-facing interfaces inject crafted SQL against the back-end database, potentially viewing, adding, modifying, or deleting its contents (CVSS 3.1 base 9.8, vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). No public exploit code has been identified at time of analysis, and EPSS is low at 0.27% (17th percentile), so real-world exploitation appears opportunistic rather than widespread despite the maximum severity rating. Impact is exposure-dependent: internet-reachable or broadly accessible management/collector instances carry the full unauthenticated risk, while deployments confined to isolated management networks are substantially less exposed. The vendor has published remediation through IBM Support.
Man-in-the-middle interception of TLS-protected communications in IBM Guardium Data Protection 12.2.2 is possible because the product does not properly validate certificates (CWE-295), allowing an attacker positioned on the network path to read and modify traffic that the software treats as trusted. The flaw is unauthenticated (CVSS 3.1 AV:N/AC:H/PR:N/UI:N) but not trivially automatable, since the attacker must first achieve an active interception position - the reason CISA SSVC rates exploitation as none and automatable as no, and the reason the assessed impact is limited to confidentiality and integrity (C:H/I:H/A:N) rather than availability. EPSS is very low at 0.14% (3rd percentile), no public exploit code has been identified, and the issue does not appear in CISA KEV; IBM has released a vendor patch, so the practical risk for most deployments is remediation-tracking rather than emergency response.
Remote code execution in IBM Guardium Data Protection 12.0, 12.1, and 12.2 is possible through a stack-based buffer overflow (CWE-121) in reachable product code, with the vendor CVSS vector indicating a network-accessible, unauthenticated trigger and no required user interaction (AV:N/PR:N/UI:N) and a maximum impact rating of 9.8. Our independent assessment scores the same impact but raises attack complexity to High (AC:H), reflecting that reliable code execution likely requires an attacker to defeat standard memory protections such as stack canaries, ASLR, and DEP, and CISA's SSVC framework rates the issue non-automatable with no observed exploitation; no public exploit identified at time of analysis, and EPSS is low at 0.37% (29th percentile). The practical picture is a high-severity, patch-priority issue rather than an emergency: the vulnerable code is assumed reachable in standard deployments since the advisory names no special prerequisite, but exposure is confined to environments running the three named 12.x releases and the vendor fix closes the window once applied.
OS command injection in IBM Guardium Data Protection 12.2.2 and 12.1 lets a remote attacker execute arbitrary operating-system commands with the privileges of the vulnerable service, yielding a full compromise of confidentiality, integrity, and availability (CVSS 9.8, CWE-78). The CVSS vector rates the flaw as unauthenticated (PR:N) over the network (AV:N) with no user interaction, although IBM's own text does not confirm whether a valid console or API session is needed to reach the vulnerable command path, and the practical risk is narrowed by the fact that Guardium appliances are normally deployed on internal management networks rather than being internet-facing. As of analysis, there is no public exploit code identified, EPSS is low at 0.36% (28th percentile), CISA SSVC records Exploitation: none with Automatable: no, and there is no KEV listing, so the dominant driver of urgency is the severity of impact if an attacker does obtain a path to the interface rather than observed exploitation.
Crafted TDS PRELOGIN packets traversing a network segment monitored by an IBM Guardium Data Protection 12.0, 12.1, or 12.2 Collector trigger a buffer overrun in the appliance's Microsoft SQL Server protocol decoder, reliably causing denial of service and, per the vendor, potentially allowing arbitrary code execution on the Collector itself. Exploitation is unauthenticated (CVSS vector PR:N) and requires no user interaction, but it depends on the attacker's ability to place a malformed packet onto the monitored database network rather than reaching a directly addressable service, because the Collector inspects traffic passively. No public exploit code has been identified at time of analysis and EPSS is low at 0.36% (28th percentile); IBM has published a vendor fix, and CISA's SSVC assessment records no observed exploitation.
Remote code execution in IBM Guardium Data Protection 12.0, 12.1, and 12.2 allows unauthenticated network attackers to trigger a buffer overflow and execute arbitrary code, with total confidentiality, integrity, and availability impact as assessed by CVSS 3.1 base 9.8 (AV:N/AC:L/PR:N/UI:N). No public exploit code or active exploitation has been identified at time of analysis; EPSS is low (0.37%, 29th percentile), and CISA SSVC marks the attack as not automatable, meaning exploitation would likely require target-specific effort. A vendor patch is available per IBM advisory node/7291674.
SQL injection in IBM Guardium Data Protection 12.1 and 12.2.2 allows unauthenticated remote attackers to execute arbitrary SQL commands against the platform's underlying data store, with IBM's own vector (AV:N/AC:L/PR:N/UI:N, C/I/A:H) describing total loss of confidentiality, integrity, and availability for exposed instances. The headline 9.8 CVSS should be tempered by conflicting signals: EPSS is only 0.30% (20th percentile), and CISA's SSVC assessment records exploitation as 'none' with the attack rated non-automatable, with no public exploit code or KEV listing identified at time of analysis. Real-world risk is governed by reachability - exploitation requires network access to a vulnerable Guardium management or collector interface, which is normally confined to restricted internal management networks rather than the internet.
Remote code execution in IBM Guardium Data Protection 12.0, 12.1, and 12.2 is achievable by an unauthenticated remote attacker (CVSS PR:N, UI:N) through a buffer overflow that corrupts memory in a way that can be leveraged to run arbitrary code, yielding high confidentiality, integrity, and availability impact (CVSS 8.1). Attack complexity is High (AC:H), so reliable exploitation depends on conditions outside the attacker's control - such as precise memory layout, timing, or a specific non-trivial input path - which tempers the practical risk despite the elevated base score. Only the listed 12.x branches are affected and patched builds are not exploitable; no public exploit code has been identified at time of analysis and there is no CISA KEV confirmation of active exploitation.
Missing authentication on a critical management function in IBM Guardium Data Protection 12.2 and 12.2.2 allows unauthenticated remote attackers to invoke arbitrary management operations against the affected appliance, with the highest possible impact to confidentiality, integrity, and availability (CVSS 9.8, AV:N/AC:L/PR:N/UI:N). Because the CVSS vector specifies PR:N with no user interaction and no non-default configuration prerequisite, any network-reachable management interface or API endpoint on an affected version is potentially exploitable without credentials; the practical constraint is reachability, since Guardium management planes are typically confined to internal or dedicated management segments. At time of analysis there is no CISA KEV entry and no publicly available exploit code identified, so exploitation is assessed as technically straightforward but not yet observed in external telemetry.
Remote code execution is possible in IBM Guardium Data Protection 12.0, 12.1, and 12.2 through a buffer overflow (CWE-119) triggered over the network, but exploitation requires valid low-privileged credentials (CVSS 3.1 AV:N/AC:L/PR:L/UI:N, base 8.8) - this is not an unauthenticated flaw, so an attacker must already hold an account or captured credential on the appliance. A successful exploit yields full compromise of confidentiality, integrity, and availability of the affected system, making privileged accounts and network reachability the key gating factors. Exploitation status is benign-to-moderate: no public exploit code has been identified and no confirmed in-the-wild activity is reported (EPSS 0.42%, 34th percentile; CISA SSVC exploitation: none), and IBM has published an advisory with a vendor fix, so patching is the decisive control.
IBM Guardium Data Protection 12.0, 12.1, and 12.2 ship with hard-coded credentials that a remote, unauthenticated attacker (CVSS PR:N/UI:N) can abuse to read sensitive information from the affected appliance service, yielding a high confidentiality impact with no integrity or availability loss (C:H/I:N/A:N, base 7.5). Exploitation is not trivial in practice: the attacker must first know or recover the static credential value and must be able to reach the Guardium management or data service over the network, which is typically an internal, segmented appliance rather than an internet-facing endpoint. There is no confirmed active exploitation (not in CISA KEV), no public exploit code identified at time of analysis, and EPSS is only 0.30% (21st percentile), so this rates as a genuine but moderate-priority exposure that should be scheduled rather than emergency-patched.
Information disclosure in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 (including the Security Verify Access Container and Verify Identity Access Container editions) allows unauthenticated remote attackers to read sensitive data from a network-reachable instance, per the CVSS vector AV:N/AC:L/PR:N/UI:N with confidentiality impact rated High and no integrity or availability effect. No public exploit code has been identified and CISA's SSVC assessment records no observed exploitation, with the attack classified as not automatable and only partial technical impact, indicating targeted rather than mass-scannable abuse. Vendor-released fixes are available from IBM, so exposure is primarily a function of how reachable the identity appliance or container endpoints are from untrusted networks.
Improper authorization enforcement in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 can allow unauthenticated remote attackers (PR:N, UI:N) to bypass access controls and alter protected content or state (I:H, C:N, A:N) when the product is deployed in front of certain web servers. The flaw, however, is configuration-dependent: as reflected by the AV:N/AC:H vector and IBM's scoping to 'some' web servers, only specific protected web-server integrations are exposed, and default or unaffected setups are not exploitable. No public exploit code or confirmed active exploitation was identified at time of analysis, and IBM rates the issue 5.9 (moderate); the affected deployments also include the containerized editions of both products.
Authentication bypass in IBM Security Verify Access (10.0 through 10.0.9.2) and IBM Verify Identity Access (11.0 through 11.0.3), including their container editions, allows a remote, unauthenticated attacker to defeat security restrictions and gain unauthorized access to functionality that should be protected. With a CVSS 3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N, C:N/I:H/A:N), the flaw is network-reachable, low complexity, and requires no credentials or user interaction; the impact is rated as high on integrity, meaning an attacker can alter protected data or configuration through the bypass. The only practical precondition is that the affected authentication or management interface be reachable by the attacker. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (not listed in CISA KEV); a vendor patch is available per IBM advisory node 7291628.
Remote code execution is possible in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3, including the containerized editions of both products, because a protection mechanism fails to prevent an authenticated principal from influencing code execution paths. Successful exploitation requires only a valid low-privilege account and network access to the product interface (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 8.8) - no user interaction or race condition is needed - and yields full compromise of confidentiality, integrity and availability of the affected instance. At the time of analysis, no public exploit code has been identified for this CVE and there is no confirmed active exploitation, but the low attack complexity and the fact that the affected systems are identity and access management infrastructure make the issue a high-priority patching target; IBM has published a vendor remediation advisory.
Authenticated argument injection in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 (including the containerized editions) allows a remote attacker who already holds valid credentials to slip crafted parameters into command or process arguments and trigger unauthorized actions, with high impact to confidentiality, integrity, and availability (CVSS 8.8). Exploitation requires authenticated access (CVSS vector PR:L) and no user interaction (UI:N), so the exposed population is limited to existing platform users rather than anonymous internet traffic. No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited (no CISA KEV listing), but a vendor patch is available and the affected systems are typically high-value identity infrastructure, making prompt remediation worthwhile.
Authentication bypass in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 (including the container editions) allows a remote, unauthenticated attacker to defeat the product's authentication control entirely, with no user interaction required. The 7.5 CVSS score reflects a high integrity impact only - the vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N) assigns no confidentiality or availability impact - so the practical effect is that an attacker can perform authenticated actions with the privileges of a legitimate session while exposing no data directly. IBM has published a vendor fix via support node 7291628, and no public exploit code has been identified at time of analysis; this is a credible operational priority but not a confirmed emergency.
Unauthenticated remote attackers can render IBM Security Verify Access (10.0 through 10.0.9.2) and IBM Verify Identity Access (11.0 through 11.0.3), including their container editions, unavailable by driving the software into uncontrolled recursion - a stack-exhausting condition with availability-only impact (CVSS 3.1 7.5, AV:N/AC:L/PR:N/UI:N/C:N/I:N/A:H). Because the vector specifies PR:N/UI:N, no credentials, user interaction, or special configuration are prerequisites, so any network-reachable, unpatched instance is a candidate and exposure management is the primary limiting factor; attacks against non-internet-facing deployments placed behind rate-limiting proxies are substantially harder to sustain. No public exploit code has been identified at time of analysis, and CISA's SSVC assessment records Exploitation: none and Automatable: no with partial technical impact, so this should be treated as a high-availability-risk but not currently exploited issue.
Path traversal (CWE-22) in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 allows a remote, unauthenticated attacker to write arbitrary files on the affected appliance or container by supplying crafted path components. Per the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N, 7.5) exploitation is network-reachable, low-complexity and unauthenticated, with high integrity impact and no confirmed confidentiality or availability impact - a file-write primitive rather than a file-read or denial-of-service bug. No public exploit identified at time of analysis and the CVE is not listed in CISA KEV; the vendor has released a patch and the sole reference is IBM's advisory at https://www.ibm.com/support/pages/node/7291628. Exposure is bounded by network reachability: instances sitting behind reverse proxies or confined to internal/DMZ segments that attackers cannot reach are not directly exploitable.
Arbitrary command execution in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 (including their container images) allows a remote attacker holding a valid low-privilege account to run commands on the underlying system by slipping argument delimiters into data that is passed to a backend process without neutralization (CWE-88). The CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (8.8) means the attack is network-reachable with no user interaction and yields full loss of confidentiality, integrity, and availability, but exploitation is not possible fully unauthenticated - the attacker must already have credentials, which narrows the realistic threat to insiders, compromised low-privilege accounts, and post-compromise escalation. There is no public exploit identified at time of analysis, though the vendor has published a patch, so unpatched deployments within the affected ranges should be treated as exposed to any authenticated user.
Cross-site request forgery in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 (including their container editions) lets a remote attacker who lures a logged-in user into loading attacker-controlled content submit unauthorized, privileged state-changing requests through that victim's authenticated session; CVSS 3.1 rates it 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). The attacker needs no credentials of their own, but successful abuse depends on a concurrently authenticated victim - most damagingly an administrator - plus a social-engineering/user-interaction step, so exposure is greatest where the management interface is internet-reachable. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (CISA KEV); a vendor patch is available per IBM's advisory.
Unauthenticated remote code execution affects IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 - including their containerized editions - through deserialization of untrusted data, allowing an attacker who can reach the affected service to run arbitrary code on the system. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 9.8) confirms the flaw is network-reachable and requires no authentication, privileges, or user interaction, so any exposed, unpatched instance should be considered directly exploitable; the only real gating factors are running an affected build and whether the vulnerable endpoint is network-accessible. No public exploit code or confirmed active exploitation has been identified at time of analysis, but a vendor patch is available and the pre-authentication nature of the issue places it in the highest remediation priority tier.
Remote code execution is achievable in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3, including their container editions, because the affected services deserialize untrusted data received over the network. The flaw is reachable without authentication and without user interaction (CVSS 3.1 base 9.8, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), allowing an attacker who can reach the vulnerable endpoint to run arbitrary code with the privileges of the affected process. There is no public exploit identified at time of analysis and the issue is not confirmed as actively exploited (CISA KEV), but a vendor patch is available and the only practical barrier to exploitation is network reachability of the exposed service.
Arbitrary code execution is possible in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 (including their container editions) when an attacker who already holds administrative privileges on the appliance and can reach the local management interface supplies input that overflows a fixed-size stack buffer. The assessed CVSS 3.1 base score is 7.2 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) with CWE-787 as the root cause, so the flaw is high-severity on impact but gated by a strong prerequisite: administrative control of the management plane rather than unauthenticated reach. Patch available per vendor advisory (IBM support page node/7291628); there is no CISA KEV entry and no public exploit code identified at time of analysis, and CISA SSVC decision points record Exploitation: none, Automatable: no, Technical Impact: partial.
An out-of-bounds read in the TDS7 LOGIN7 protocol parser of IBM Guardium Data Protection 12.0, 12.1, and 12.2 allows unauthenticated remote attackers to deliver a crafted LOGIN7 packet with invalid offset or length values, causing denial of service and limited memory disclosure. The published CVSS 3.1 score is 9.1, but our independent assessment reduces confidentiality to Low (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H), and with EPSS at only 0.29% (20th percentile), no CISA KEV listing, and no public exploit identified at time of analysis, real-world priority is lower than the headline score suggests even though technical impact is rated total. The dominant limiting factor is network reachability: only deployments whose TDS/database-interception listener is exposed to untrusted networks are practically at risk.
Remote, unauthenticated memory corruption in IBM Guardium Data Protection 12.0, 12.1, and 12.2 allows an attacker who can reach a monitored MongoDB data path to overflow a heap buffer in the product's MongoDB protocol parser and potentially crash the appliance or execute arbitrary code. The flaw is triggered by a MongoDB SCRAM authentication message carrying an oversized username field, and because the parser runs inside the inspection engine, exposure is limited to deployments where Guardium's S-TAP/collector is actively inspecting MongoDB traffic. The vendor-rated CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, 9.8) describes a pre-authentication, low-complexity flaw with full confidentiality, integrity, and availability impact, though no public exploit code has been identified at time of analysis and reliable code execution (as opposed to a denial-of-service crash) is constrained by heap-exploitation difficulty.
A heap-based buffer overflow in IBM Guardium Data Protection's S-TAP TrafficTap TDS login reassembly routine allows an unauthenticated remote attacker to crash the agent or potentially execute arbitrary code by sending crafted TDS login fragments that overflow the fixed-size reassembly buffer. Affected deployments are Guardium Data Protection (S-TAP agent) versions 12.0 and 12.1, with EUVD additionally listing 12.2; exploitation requires the S-TAP agent to be actively inspecting TDS traffic on a reachable database-communication path, so exposure is limited to networks where an attacker can inject traffic into monitored Microsoft SQL Server or Sybase/SAP ASE sessions. The vendor rates this CVSS 3.1 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), and no public exploit code or confirmed active exploitation was identified at time of analysis.
Local privilege escalation in Guardium Data Protection 12.2 allows an authenticated low-privileged local user to abuse the cp_wrapper component to gain root privileges and access or modify sensitive system files. The issue is not remotely exploitable (AV:L) and requires a pre-existing local foothold (PR:L), so it is most relevant to insider threats, compromised low-privileged accounts, and post-compromise escalation; no public exploit identified at time of analysis, and no CISA KEV confirmation was provided. IBM has released a vendor patch, and this is a credible but not emergency-tier priority.
Local privilege escalation in IBM Guardium Data Protection 12.2 allows an attacker who already holds low-privilege local access on the appliance to recover the root password through the pkcrypto passkey component and thereby obtain full root control, because that component combines weak cryptographic protection with a hard-coded recovery key (CWE-798). The exposure is confined to a local attack path (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning no network or unauthenticated remote vector exists and the attacker must first establish a foothold on the appliance - realistically an insider or someone who has already compromised the host by other means. There is no public exploit identified at time of analysis, CISA SSVC rates exploitation as none and the flaw as non-automatable while assigning total technical impact, and EPSS is 0.11% (1st percentile), so this is a serious but not urgent technical issue.
Local privilege escalation to root in the IBM Guardium Data Protection 12.2 patch installer, where a signature-verification bypass lets an attacker substitute a tampered or unsigned patch artifact that the installer then executes with root privileges. Exploitation requires local access to the appliance with at least low-level privileges (PR:L) and the ability to stage a malicious patch and win a timing window during installation; the assessed vector is AV:L/AC:H with a resulting base score of roughly 7.0, slightly below the vendor-published 7.8. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the vendor has published a patch; this is a credible but not emergency-tier priority given the local-only attack path, prerequisite foothold, and race-condition reliability constraints.
Missing authentication in the edge-controller component of IBM Guardium Data Protection 12.1 and 12.2.2 allows unauthenticated remote attackers to push and execute arbitrary container images, which in turn grants control over the managed edge clusters that component orchestrates. The flaw is rated 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) for the base case and was independently assessed with scope-changed impact (S:C), reflecting that compromise of the controller extends to the clusters it manages; no credentials, privileges, or user interaction are required against a reachable instance. No public exploit code has been identified at the time of analysis and the issue has not been confirmed as actively exploited (CISA KEV), so the practical risk is driven by network exposure of the edge-controller interface rather than by an observed campaign; a vendor patch is available from IBM.
Unauthenticated path traversal in IBM Guardium Data Protection 12.2 allows a remote attacker who can reach the GIM (Guardium Installation Manager) file-upload interface to escape the intended upload directory and write arbitrary files onto a Collector host. The assessed vector (AV:N/AC:L/PR:N/UI:N, integrity impact) confirms that no credentials or user interaction are required against that endpoint, so any 12.2 Collector whose GIM upload service is reachable is exposed until patched; the practical attack surface is driven almost entirely by network segmentation of GIM. No public exploit code has been identified at time of analysis, and exploitation has not been confirmed as active - impact is file-system write access on the Collector, scoring CVSS 7.5.
Denial of service in IBM Guardium Data Protection 12.2.2 allows an unauthenticated remote attacker with network reachability to the edge-controller gRPC service to terminate the edge-controller process by supplying malformed task data that trips an unchecked type assertion. The assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, score 7.5) confirms no authentication, no user interaction, and no special timing are required once the port is exposed, and impact is confined to availability - the process crashes unexpectedly with no data disclosure or modification. There is no public exploit identified at time of analysis and no confirmed active exploitation (the CVE is not in CISA KEV), so the practical exposure is governed by reachability: deployments that keep the edge-controller gRPC endpoint on isolated management networks are not exposed to arbitrary remote attackers, while internet- or broad-LAN-accessible instances are at meaningful disruption risk. The primary limiting factor is that the gRPC port must be reachable, making this a genuine but bounded-impact availability issue.
Local privilege escalation in IBM Guardium Data Protection 12.2 lets an already-authenticated, high-privileged user gain root-level command execution by feeding attacker-controlled arguments to the SUID-root ssh_config_wrapper component. Because the component runs with effective UID 0, successful argument injection converts a privileged-but-limited foothold into full root control of the appliance, with high impact to confidentiality, integrity, and availability. This is a moderate-severity escalation issue rather than a remote-takeover emergency: the attacker must already hold a high-privileged account and be able to invoke the vulnerable binary locally, and no public exploit code has been identified at time of analysis. A vendor patch is available, though the specific fixed build is not enumerated in the supplied data.
Unauthenticated remote code execution in IBM DataPower Gateway affects the 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2 release trains, where a heap-based buffer overflow caused by improper bounds checking lets an attacker who can reach the appliance's request-processing path corrupt heap memory and run arbitrary code with full confidentiality, integrity and availability impact. The flaw is rated CVSS v3.1 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), meaning no authentication or user interaction is required, and it is exploitable over the network. There is no public exploit identified at time of analysis and it is not confirmed actively exploited (no CISA KEV listing); IBM has published a vendor fix, and this is a genuine high-priority issue rather than an inflated high-CVSS score.
Unauthenticated remote attackers can trigger a memory-safety fault in IBM DataPower Gateway that crashes the affected service, producing a denial-of-service condition; the assessed CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H, score 8.2) confirms network reachability with no authentication, no user interaction, and no unusual configuration required, while availability impact is High and there is a limited Confidentiality impact from potential leakage of adjacent memory. Affected releases are 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2. This issue is not confirmed as actively exploited (no CISA KEV listing) and no public exploit code has been identified at time of analysis, but a vendor patch is available and the affected versions are frequently internet-facing, so prioritization should follow normal critical-exposure timelines rather than emergency response.
Security-restriction bypass in IBM DataPower Gateway 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2 allows a remote authenticated attacker to have forged or tampered cryptographic signatures accepted by the gateway, defeating the trust checks those signatures are meant to enforce. Per the assessed vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N, 8.1), the attacker must already hold valid low-privilege credentials and have network reachability to the gateway, but no user interaction is required, and successful exploitation yields high confidentiality and integrity impact with no availability effect. No public exploit code was identified at time of analysis, and the issue is not confirmed as actively exploited (CISA KEV); the primary limiting factor is the authentication prerequisite, which excludes fully unauthenticated external attackers.
Empty-password LDAP authentication bypass in IBM DataPower Gateway lets remote, unauthenticated attackers obtain administrative access to affected appliances by submitting a blank password that the LDAP authentication logic fails to reject. The flaw carries a CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and affects 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2; exploitation requires only that LDAP be configured for administrative/management authentication and that the authentication interface be network-reachable. At time of analysis there is no public exploit identified, but IBM has published a vendor fix, and the combination of network-only attack surface, no authentication prerequisite, and full confidentiality/integrity/availability impact warrants emergency-level prioritization in any environment using LDAP-backed management logins.
Denial of service in IBM DataPower Gateway 11.0.0.0 through 11.0.0.2 allows an attacker who already holds a valid low-privileged account to trigger improper memory allocation during key derivation, corrupting memory and rendering the gateway unavailable (CVSS 7.7, AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H). Because the vector requires PR:L, the flaw is not exploitable pre-authentication, and its scope-changed rating reflects that the availability impact can extend past the initially compromised security boundary; there is no confidentiality or integrity impact. Patch available per vendor advisory and no public exploit identified at time of analysis, so risk is concentrated in unpatched appliances where an attacker can obtain even limited authenticated access.
Unauthenticated remote attackers can trigger a use-after-free in IBM DataPower Gateway, resulting in a denial of service and potential disclosure of sensitive information held in freed memory. The flaw affects the 10.5.0 branch (10.5.0.0 through 10.5.0.22), the 10.6.0 branch (10.6.0.0 through 10.6.0.10), the 10.6CD/10.6.1 branch (10.6.1 through 10.6.6), and the 11.0.0 branch (11.0.0.0 through 11.0.0.2); the CVSS vector (AV:N/AC:L/PR:N/UI:N, C:H/I:N/A:H) rates it 9.1, but exploitation requires the gateway endpoint to be network-reachable and, as a memory-safety bug, reliable triggering typically depends on request sequencing and allocator/timing state. There is no public exploit identified at time of analysis, EPSS is low at 0.24% (14th percentile), and CISA's SSVC framework records exploitation as none and automatable as no - signals are therefore mixed between a high headline severity score and a low observed exploitation likelihood. A vendor patch is available per IBM's advisory.
Remote code execution in IBM DataPower Gateway (10.5.0.0-10.5.0.22, 10.6.0.0-10.6.0.10, 10.6.1-10.6.6, and 11.0.0.0-11.0.0.2) is caused by a heap-based buffer overflow that a remote attacker can trigger without authentication or user interaction, carrying a CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N) with total impact to confidentiality, integrity, and availability. Exploitation is not confirmed by any signal: no public exploit code has been identified at time of analysis, the issue is not listed in CISA KEV, SSVC reports Exploitation=none with Automatable=no, and EPSS is only 0.37% (29th percentile). The practical risk therefore hinges on whether affected DataPower builds are reachable from untrusted networks, since IBM has published a fix and the high base score reflects worst-case impact rather than observed attack activity.
XML external entity injection in IBM DataPower Gateway 10.5.0.0-10.5.0.22, 10.6.0.0-10.6.0.10, 10.6.1-10.6.6, and 11.0.0.0-11.0.0.2 lets remote, unauthenticated attackers who can reach an XML-accepting endpoint read files or internal resources from the gateway host and, via entity expansion, exhaust memory. The CVSS:3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L, base 8.2) confirms no credentials or user interaction are required, with high confidentiality impact and low availability impact. There is no public exploit code and no indication of active exploitation, and IBM has published a patch through its support portal.
Out-of-bounds memory handling in IBM DataPower Gateway (10.5.0.0 through 10.5.0.22, 10.6.1 through 10.6.6, 10.6.0.0 through 10.6.0.10, and 11.0.0.0 through 11.0.0.2) allows network attackers to trigger a buffer overflow that can disclose sensitive process memory or crash the appliance. Per the assessed vector (AV:N/AC:L/PR:N/UI:N), exploitation is unauthenticated and requires no user interaction, with high confidentiality and availability impact but no integrity impact - consistent with the CWE-125 out-of-bounds read classification rather than a write-based code-execution primitive. No public exploit code was identified at time of analysis, CISA SSVC records exploitation as 'none' and automation as 'no', and EPSS is low at 0.22% (12th percentile); note that the vendor's own 9.8 rating assumes full C/I/A impact, which this assessment does not corroborate. Patch available per vendor advisory (IBM support page node/7289775).
Authentication bypass in IBM DataPower Gateway lets remote, unauthenticated attackers forge JSON Web Signatures and present themselves as a trusted, already-verified identity on gateways that use JWS/JWT signature verification for access control. Affected releases are 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2; per the assessed CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N, base 7.5) exploitation requires no credentials or user interaction and the impact is integrity-only, meaning the payoff is forged trust and unauthorized access rather than direct data disclosure. No public exploit identified at time of analysis, EPSS is low at 0.20% (9th percentile), and the CISA SSVC assessment records exploitation as none with automation not feasible, so this is a genuine but moderate-priority issue rather than a top-tier emergency; vendor patches are nonetheless available.
A remotely reachable, unauthenticated out-of-bounds write (buffer overflow, CWE-787) in IBM DataPower Gateway can corrupt memory and potentially allow an attacker to fully compromise the affected appliance, as reflected in the assessed CVSS 3.1 score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). Affected firmware spans 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2, with the flaw reachable in the normal network-processing path since no authentication, user interaction, or special configuration is required. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation, though the unauthenticated network attack surface and memory-corruption impact make this a genuine high-priority issue for exposed deployments; IBM has published a vendor fix via its support advisory.
Cross-site scripting in the IBM DataPower Gateway 10.6.0 Web UI (builds 10.6.0.0 through 10.6.0.10) lets an unauthenticated attacker inject arbitrary JavaScript that executes in the browser of an operator who is already logged into the appliance management console, potentially leading to credential or session disclosure within that trusted session. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N, 9.3) confirms the attacker needs no credentials but the victim must interact with attacker-supplied content, so this is a lure-driven, high-impact issue rather than silent mass exploitation; no public exploit has been identified at time of analysis. A vendor patch is available, and only the 10.6.0.x range up to 10.6.0.10 is affected, so upgrading the fixed build removes exposure.
Arbitrary code execution in IBM DataPower Gateway is possible when a user with existing local access to the appliance supplies crafted oversized input to a component that performs improper bounds checking, allowing an out-of-bounds write and, potentially, execution of arbitrary code in the appliance's process context. Affected release trains are 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2; IBM has published a vendor fix, and no public exploit code was identified at time of analysis. Note that the vendor-assigned CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N, score 9.8) characterizes this as remotely exploitable without privileges, which is inconsistent with the description's requirement for a local user and with the independent assessment of AV:L/AC:L/PR:L/UI:N - the local-access prerequisite is the practical limiter on real-world risk, while the impact if triggered remains full confidentiality, integrity, and availability loss.
Stack-based buffer overflow in IBM DataPower Gateway firmware tracks 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2 allows an authenticated attacker holding administrative-level privileges to execute arbitrary code on the gateway. Exploitation is network reachable but gated by high attack complexity (AC:H), meaning the attacker depends on conditions they cannot fully control, such as a specific memory layout or parsing state, so a single deterministic trigger is not guaranteed; the assessed vector is CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H. There is no public exploit identified at time of analysis and the issue is not reported as confirmed actively exploited (CISA KEV); IBM has released patched builds via its support advisory.
Out-of-bounds write in IBM DataPower Gateway lets a remote, unauthenticated attacker corrupt memory and potentially execute arbitrary code on affected gateway builds (10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2), as reflected in the CVSS v3.1 vector AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H and a base score of 8.1. The PR:N/UI:N components mean no credentials or user interaction are required, so any network-reachable instance on an affected build is exposed, though the AC:H rating indicates exploitation depends on satisfying a non-trivial condition - most likely a specific input state, parsing path, or memory layout - to escalate the write beyond a crash into reliable code execution. Vendor patch data indicates a fix is available from IBM, and no public exploit code or confirmed active exploitation was identified at time of analysis; the EPSS score was not provided in the underlying intelligence, so no probabilistic exploitation estimate can be quoted.
Unauthenticated remote code execution affects IBM DataPower Gateway across multiple release streams - 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2 - stemming from an out-of-bounds write (CWE-787) that corrupts memory and can be leveraged to run attacker-controlled code. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, 9.8) confirms the flaw is reachable over the network with no authentication and no user interaction, making any internet- or partner-facing DataPower instance running an unpatched build a high-priority target. Exploitation status: no public exploit identified at time of analysis, and the issue is not listed in CISA KEV; patch available per vendor advisory (IBM support page node/7289775), with the specific fixed firmware builds published there.
IBM DataPower Gateway can be driven into a denial-of-service condition by a remote, unauthenticated attacker who supplies input that reaches a flawed sorting comparator, causing the comparator to violate strict-weak-ordering and triggering an out-of-bounds memory access (CWE-787) that can crash or destabilize the affected service. All builds in the 10.5.0.0-10.5.0.22, 10.6.0.0-10.6.0.10, 10.6.1-10.6.6, and 11.0.0.0-11.0.0.2 ranges are affected; the impact is confined to availability (CVSS 3.1 base 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) with no confidentiality or integrity effect and no privilege gain. At time of analysis there is no confirmed active exploitation (not in CISA KEV) and no public exploit code identified, and IBM has published a fix via its support advisory, so this should be treated as a patching-priority availability risk rather than an emergency.
Unauthenticated remote attackers can drive IBM DataPower Gateway into resource exhaustion and denial of service by sending crafted GraphQL queries that abuse improper memoization of fragment spreads. Affected releases are 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2, and per the CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H vector no authentication or user interaction is required once a reachable GraphQL-processing endpoint exists. Impact is confined to availability (no confidentiality or integrity loss), and there is no public exploit identified at time of analysis; exposure depends entirely on whether the gateway has been configured to accept and process GraphQL requests.
Heap-based buffer overflow (CWE-787) in IBM DataPower Gateway allows an unauthenticated remote attacker to crash the gateway and cause a denial of service. Affected builds are 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2; per the CVSS vector (AV:N/AC:L/PR:N/UI:N) no credentials or user interaction are required, so any attacker who can reach a listening interface and deliver a crafted request to the vulnerable parsing path can trigger the fault. The assessed impact is availability-only (A:H, C:N/I:N) rated 8.2 High; no public exploit code and no confirmed active exploitation were identified at time of analysis, and the practical risk is governed mainly by network exposure of the gateway's listening interfaces. This is a genuine but tier-two priority issue rather than an emergency, with patches available from IBM.
A type confusion flaw (CWE-843) in IBM DataPower Gateway lets a remote, unauthenticated attacker crash a reachable gateway service, producing a denial-of-service condition. Affected builds are 10.5.0.0 through 10.5.0.22, 10.6.1 through 10.6.6, 10.6.0.0 through 10.6.0.10, and 11.0.0.0 through 11.0.0.2; the assessed CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, base 7.5) confirms a network-reachable, low-complexity, unauthenticated trigger with availability-only impact. IBM has published a vendor fix via its support advisory, and no public exploit code has been identified at time of analysis (no CISA KEV listing).
Out-of-bounds write in IBM DataPower Gateway lets unauthenticated remote attackers corrupt process memory, resulting in disclosure of sensitive information and denial of service. Affected releases are 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2, with a CVSS 3.1 base score of 8.6 driven by high availability impact alongside limited confidentiality and integrity impact. No public exploit code has been identified at time of analysis, and IBM has made a fix available through its support advisory, so this is a credible operational priority rather than a confirmed emergency - exposure depends on whether the gateway's network listeners are reachable by the attacker.
IBM DataPower Gateway is vulnerable to a remote, unauthenticated denial of service (CVSS 3.1 base 7.5) in which a crafted request triggers an out-of-bounds read, degrading or crashing the affected gateway service. All supported firmware streams in the affected ranges are exposed: 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6 (the 10.6 CD stream), and 11.0.0.0 through 11.0.0.2. The vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) confirms exploitable over the network with no authentication, privileges, or user interaction, but restricts impact to availability - no confidentiality or integrity loss is assessed - so exploitation results in service disruption rather than compromise; there is no public exploit identified at time of analysis, and a vendor patch is available.
Denial of service in IBM DataPower Gateway affects releases 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2, where crafted network input reaching the vulnerable parsing path overflows a buffer and can crash the affected service. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), exploitation requires no authentication and no user interaction, so any internet- or partner-facing listener that processes malformed input is exposed; impact is availability-only - a crash/restart condition rather than data exposure or code execution. No public exploit code has been identified at time of analysis and the flaw is not listed as confirmed actively exploited (CISA KEV), so this is a genuine but bounded operational risk that depends primarily on whether affected listeners are reachable from untrusted networks.
Unauthenticated remote attackers can crash IBM DataPower Gateway by sending a crafted request that triggers a null pointer dereference, resulting in a denial of service that takes the affected service interface offline. All four maintained release trains are affected: 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N) no authentication, user interaction, or privileged position is needed - only network reachability to a vulnerable, unpatched gateway - and the sole impact is availability (C:N/I:N/A:H), with no data exposure or code execution. No public exploit code or confirmed active exploitation was identified at time of analysis, so this is a credible but bounded availability risk that is governed primarily by how exposed the gateway's service interfaces are to untrusted networks.
An out-of-bounds write in IBM DataPower Gateway (10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2) allows an unauthenticated remote attacker to corrupt gateway memory, most reliably causing a denial of service and potentially enabling partial confidentiality or integrity compromise. The flaw carries a CVSS 3.1 base score of 8.6 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H), and the vector's PR:N/UI:N components confirm no credentials or user interaction are required to reach the vulnerable code - the practical limiting factor is whether the attacker's network can reach a DataPower service listener. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the vendor has published a fix via IBM Support (node/7289775).
Remote, unauthenticated code execution is possible in IBM DataPower Gateway versions 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2, because an out-of-bounds write in the RFC2047 encoded-word parser can corrupt memory and be leveraged to run arbitrary code. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N, base 9.8) indicates the flaw is network-reachable with low complexity, requires no credentials and no user interaction, and carries full confidentiality, integrity, and availability impact, though exploitation depends on a reachable service or flow that passes attacker-controlled data through MIME encoded-word decoding. According to available intelligence there is no confirmed active exploitation (not listed in CISA KEV) and no public exploit code identified at time of analysis; the primary source is IBM's advisory at https://www.ibm.com/support/pages/node/7289775.
Security restriction bypass in IBM DataPower Gateway leaves the appliance's authorization logic exploitable by unauthenticated remote attackers, allowing them to reach functionality or data that should have required elevated privileges. Affected builds are 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2; the CVSS 3.1 vector (7.4, AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N) confirms the attack is network-reachable with no credentials and no user interaction, but the high attack-complexity component means some condition outside the attacker's control - such as a particular request sequence, timing, or policy/configuration state - must be satisfied first, and the gateway service must be network-reachable at all. IBM's own PSIRT reported the issue and no public exploit code or confirmed active exploitation has been identified at time of analysis; impact is scored high for confidentiality and integrity with no availability impact, so the practical risk is unauthorized read/modification of gateway-mediated data or configuration rather than denial of service.
A heap buffer underwrite in IBM DataPower Gateway allows unauthenticated remote attackers to crash the gateway service, producing a denial-of-service condition on affected appliances. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N), the flaw is reachable over the network with no privileges or user interaction required, and impact is confined to availability (C:N/I:N/A:H). Affected firmware spans 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2; no public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV.
Denial of service in IBM DataPower Gateway allows a remote, unauthenticated attacker to crash or degrade an affected gateway by sending crafted input that the product fails to validate correctly, resulting in an out-of-bounds write in memory. All four supported release trains are affected: 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, score 7.5) confirms the attack is launched over the network with no authentication and no user interaction, and that the sole impact is availability - there is no confidentiality or integrity loss, so the risk is bounded to service outage on gateways whose vulnerable interface is reachable from untrusted networks. No public exploit code has been identified at time of analysis, no EPSS score was supplied, and CISA KEV does not list this CVE.
Denial of service in IBM DataPower Gateway allows a remote, unauthenticated attacker to crash or exhaust the message-processing service by sending crafted messages whose length field is mishandled during memory reallocation. All firmware levels in the ranges 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2 are affected; the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, score 7.5) indicates no authentication, user interaction, or non-default configuration is needed, and the only impact is loss of availability. There is no confirmed active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis, but because exploitation only requires network reachability to the gateway's message interface, internet- or partner-facing appliances should be treated as the highest-priority remediation targets.
A heap buffer overflow in IBM DataPower Gateway (affected firmware levels 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2) allows remote attackers to crash the service and cause a denial of service; the CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates no authentication, privileges, or user interaction are required, so any reachable affected gateway is a candidate target. Impact is confined to availability - the vendor reports no confidentiality or integrity loss and no code execution. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (not in CISA KEV); this is a genuine availability risk but not a top-tier emergency, with practical exposure limited by how broadly the gateway's data-plane and management interfaces are reachable.
Unauthenticated remote attackers can exhaust system resources on IBM DataPower Gateway firmware releases 11.0.0.0 through 11.0.0.2, degrading or halting availability of the gateway's traffic and management services. The flaw is rated CVSS 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), meaning no credentials, user interaction, or special positioning are required once the affected interface is reachable, but impact is confined to availability - there is no data disclosure, tampering, or code execution component. No public exploit code has been identified and there is no confirmed active exploitation (not listed in CISA KEV); the practical risk is therefore a bounded denial-of-service exposure that is highest where DataPower interfaces are internet-facing or unsegmented, and much lower where they sit behind network controls and rate limiting.
Denial of service in IBM DataPower Gateway lets unauthenticated remote attackers send crafted network traffic that triggers an out-of-bounds write (CWE-787), degrading or halting the gateway's availability. The flaw affects version lines 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2, scoring CVSS 3.1 base 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) with availability-only impact. No public exploit code has been identified at time of analysis and there is no CISA KEV listing, but IBM has published a vendor fix, so internet-facing gateways should be treated as the highest-priority upgrade target.
Remote code execution affects IBM Langflow OSS versions 1.0.0 through 1.12.2, where improper access control lets an attacker with a valid low-privilege account execute arbitrary code on the server. The flaw is network-reachable with low attack complexity and no user interaction (CVSS 3.1: AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 8.8), but it is gated by the requirement to hold an authenticated account, so exposure is greatest where the platform offers open self-service registration, uses shared credentials, or is internet-facing without network restrictions. No public exploit code has been identified and the issue is not listed as confirmed actively exploited (CISA KEV) at time of analysis; exploitation status and patch availability should be re-checked against the IBM advisory.
Authenticated remote code execution affects IBM Langflow OSS 1.0.0 through 1.12.2, where improper control of code generation lets any account with at least low privileges (CVSS PR:L, AV:N, UI:N) cause attacker-supplied code to run server-side on the Langflow host, yielding high confidentiality, integrity, and availability impact (CVSS 8.8). Exploitation is not possible against a default install without valid credentials, and no public exploit code or confirmed active exploitation was identified at time of analysis. The practical exposure therefore concentrates on internet-reachable or multi-tenant instances that permit self-registration or host untrusted users; isolated, single-tenant, network-restricted deployments with trusted operators carry substantially lower risk.
Authenticated code injection in IBM Langflow OSS 1.0.0 through 1.12.2 lets any remote user holding a valid low-privileged account execute arbitrary code on the hosting server, with high impact to confidentiality, integrity, and availability (CVSS 8.8, PR:L, no user interaction required). The attack surface is the code path where special elements used in code are not properly neutralized (CWE-94), so deployments that allow untrusted or self-registered accounts to author and run flows are the most exposed, while instances with closed registration and no internet exposure are materially less at risk. No public exploit code has been identified at time of analysis, EPSS is only 0.58% (46th percentile), and CISA SSVC rates exploitation as 'none', making this a serious-but-not-emergency issue; a vendor patch is available per IBM's advisory.
Authenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.12.2 allows a low-privileged user to run arbitrary code because the platform improperly controls generation of executable code (CWE-94). Exploitation requires only a valid account on the instance (CVSS PR:L, AV:N, AC:L, UI:N), so an attacker who holds or obtains any credential able to create, import, or execute a flow/component that reaches the vulnerable code-generation path can achieve full confidentiality, integrity, and availability impact on the host. No public exploit code was identified at time of analysis, CISA's SSVC assessment records exploitation as "none", and EPSS is 0.58% (46th percentile), placing this as a genuinely serious but not emergency-tier issue whose real-world risk scales with how exposed the Langflow instance is and how freely low-privilege accounts are provisioned.
Remote code execution in IBM Langflow OSS versions 1.0.0 through 1.12.2 allows an authenticated attacker with flow-authoring privileges to inject and execute arbitrary code through Langflow's code-generation mechanism (CWE-94). The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) rates this as high severity (8.8), requiring network reachability, low privileges, and no user interaction; however, in typical deployments where flow creation or modification is broadly granted, the practical barrier may be lower than the PR:L metric implies. No public exploit code or CISA KEV entry has been identified at time of analysis, and EPSS is 0.61% (48th percentile); IBM has released a vendor patch.
Deserialization of untrusted cache data in IBM Langflow OSS 1.0.0 through 1.12.2 can execute attacker-controlled code with the privileges of the Langflow service process, but only for an attacker who has already obtained two things: the Langflow server secret and write access to the backing Redis instance used as the application cache. Because both prerequisites are effectively gated - the server secret is a trusted signing/trust value and Redis is normally bound to localhost or a private, authenticated network - this is not exploitable by an anonymous remote attacker against a default deployment, which is why the practical risk is lower than the 7.5 base score suggests. No public exploit code has been identified at time of analysis and the issue is not listed as confirmed actively exploited (CISA KEV).
Remote code execution can result in IBM Langflow OSS 1.0.0 through 1.12.2 through a dependency confusion weakness, where the product resolves an expected dependency from a public package registry instead of the intended trusted source. The CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates an unauthenticated remote attacker with no user interaction required, and the unpatched severity is rated 9.8; however, our independent assessment lowers the attack complexity to AC:H because successful exploitation depends on the attacker knowing or guessing the exact dependency name and on the victim's resolver preferring an attacker-published public package over the legitimate one, typically during an install, build, or import event rather than against a running service. There is no confirmed active exploitation (CISA KEV does not list this CVE), SSVC records Exploitation: none and Automatable: no, no public exploit code has been identified at time of analysis, and EPSS is only 0.68% (51st percentile), so the practical near-term risk is materially lower than the 9.8 headline suggests. A vendor patch is available per the IBM advisory.
Sensitive information disclosure in IBM Langflow OSS 1.0.0 through 1.12.2 allows a remote, low-privilege authenticated attacker to retrieve objects belonging to other users by manipulating a user-controlled identifier that the application fails to scope to the requesting principal (CWE-639, IDOR-style authorization bypass). The flaw is network-reachable with low attack complexity and no user interaction, but it is gated on the attacker already holding valid credentials for a low-privilege account (CVSS PR:L); the assessed impact is a high-confidentiality, read-only exposure with no demonstrated integrity or availability effect, so realistic risk concentrates in multi-user or multi-tenant Langflow deployments where a low-trust account can reach another tenant's or user's data. Patch available per vendor advisory (IBM support node 7290694); no public exploit identified at time of analysis.
Unauthenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.12.2 lets any attacker who can reach the service execute arbitrary operating system commands on the underlying host. Rated CVSS 3.1 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), the flaw requires no credentials, no user interaction, and no non-default configuration, so a default Langflow deployment exposed beyond localhost is directly exploitable. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV); IBM has published a vendor advisory with a fix, and practical risk is concentrated in self-hosted developer instances that are bound to reachable interfaces rather than being restricted to localhost or placed behind authentication and firewalling.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.12.2 lets a remote attacker who already holds a valid low-privilege session execute arbitrary code on the host by sending a crafted request that bypasses improper input validation. The flaw is network-reachable, low complexity, and requires no user interaction (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 8.8), so the authentication requirement is the main barrier; deployments with open or self-service sign-up, internet exposure, or multi-tenant use carry the highest risk. No public exploit code was identified at time of analysis and the issue is not confirmed as actively exploited (no CISA KEV listing); the vendor has released a fix.
Authenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.12.2 lets any holder of valid credentials - even a low-privileged one - submit or edit a flow that reaches the server-side code-generation and execution path, resulting in arbitrary OS command execution on the Langflow backend. IBM scores it 8.1 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N) and classifies the root cause as CWE-94 code injection; no public exploit code has been identified at time of analysis and there is no CISA KEV listing, so active exploitation is not confirmed. The decisive risk factor is deployment posture: internet-exposed or multi-tenant instances running with authentication disabled, default or shared credentials, or open self-registration collapse the PR:L barrier and behave like unauthenticated RCE targets.
Authenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.12.2 lets any user who can log in to the instance run arbitrary code on the host, because the platform fails to properly constrain attacker-supplied input before it reaches a code-execution path. 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), meaning low-complexity, network-reachable exploitation that requires only a low-privileged account but yields full confidentiality, integrity, and availability impact - no user interaction and no elevated privileges are needed. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation, but IBM has published a vendor advisory with a fix, so the practical exposure is greatest for organizations that expose Langflow to untrusted networks or provision accounts broadly.
Remote code execution in IBM Langflow OSS versions 1.0.0 through 1.12.2 allows an authenticated attacker to run arbitrary operating-system commands by supplying crafted input to a component that fails to neutralize special elements before passing them to an OS command or code-evaluation path (CWE-94). Per the assessed CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), exploitation requires a valid low-privilege authenticated session on the Langflow instance, needs no victim interaction, and yields full confidentiality, integrity, and availability impact on the affected host. No public exploit code was identified at time of analysis, and the issue is not confirmed as actively exploited (CISA KEV); the practical risk is concentrated on network-exposed Langflow servers that use weak, shared, or default credentials, since a compromised or low-privilege account is the only prerequisite.
Improper access control in the vertex result caching subsystem of IBM Langflow OSS 1.0.0 through 1.12.2 lets a remote authenticated attacker read sensitive cached data or inject malicious content into vertex results that other users then consume. The issue carries a CVSS 3.1 base score of 8.3 (High) under the vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L, meaning it is network-reachable with low complexity and requires only a low-privileged account, while yielding high confidentiality and integrity impact and low availability impact. No public exploit code has been identified at time of analysis and the flaw does not appear in CISA KEV; IBM has published a patch advisory (node/7290694), so exposure is limited to unpatched deployments and to attackers who already hold valid credentials on the instance.
Authenticated remote code execution affects IBM Langflow OSS versions 1.0.0 through 1.12.2, where an incomplete blocklist in the built-in code security scanner can be bypassed to execute arbitrary code on the server. Exploitation requires a valid low-privilege account (CVSS PR:L) and the ability to submit code evaluated by the scanner; unauthenticated attackers are not sufficient. No public exploit code has been identified at time of analysis and there is no CISA KEV listing, though the high CVSS base score of 8.8 and the multi-tenant exposure of typical Langflow deployments make the risk significant where untrusted users can register or be provisioned.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.12.2 lets an authenticated attacker escape the application's code execution sandbox and run arbitrary commands on the host. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N) confirms network reachability and a low-privileged authenticated session as the only precondition, with no user interaction required. No public exploit code has been identified at time of analysis and there is no CISA KEV entry, but the low complexity and high impact make this a genuine prioritization concern for internet-exposed or multi-tenant deployments.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.12.2 allows attackers to execute arbitrary code via improper control of code generation (CWE-94). The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 9.8) indicates remote, unauthenticated, low-complexity exploitation with full confidentiality, integrity, and availability impact, though the independent assessment notes the pre-auth condition is not independently confirmed by the description. A vendor patch is available, and no public exploit code has been identified at time of analysis; risk is highest for internet-exposed instances within the affected version range.
Local privilege escalation on IBM i 7.3, 7.4, 7.5, and 7.6 allows an attacker who already holds a valid low-privilege user profile to reassign ownership of arbitrary files by supplying an improperly validated file path. The flaw carries a CVSS 3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning exploitation requires local access and low-privilege authentication but no user interaction, and yields high confidentiality, integrity, and availability impact. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (CISA KEV); IBM has released a patch, so patched systems are not exploitable.
IBM DataStage on Cloud Pak for Data 5.4.0.0 contains a path traversal flaw in its archive extraction routine that lets a remote attacker with a valid authenticated account write files outside the intended destination directory and ultimately execute arbitrary code with the privileges of the affected service (CVSS 3.1 base 8.8, AV:N/AC:L/PR:L/UI:N/C:H/I:H/A:H). The root cause is CWE-22 improper limitation of a pathname to a restricted directory, commonly known as an archive 'zip-slip' condition, where crafted entries in an uploaded archive escape the extraction root. Authentication is mandatory, so this is not an unauthenticated flaw; no public exploit code and no confirmed active exploitation were identified at time of analysis, and the realistic risk is concentrated in enterprise Cloud Pak for Data deployments where the attacker already holds platform credentials or a foothold.
Unauthenticated path traversal in IBM Guardium Data Protection 12.0, 12.1, and 12.2 can be leveraged by remote attackers to execute arbitrary code on the affected deployment, producing a vendor CVSS 3.1 base score of 9.8 from the vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Per that vector the flaw requires no authentication, no user interaction, and no non-default configuration, so the only practical barrier is network reachability of the exposed Guardium interface; because the product is normally deployed inside segmented enterprise networks, internet-wide exposure is expected to be limited. There is no public exploit identified at time of analysis and no confirmed active exploitation, but the worst-case skill and access profile place this in the urgent patching tier for any instance reachable from untrusted networks; the specific traversal entry point and the path from traversal to code execution are not detailed in the available advisory data and should be confirmed against IBM support node 7291674.
Unauthenticated SQL injection in IBM Guardium Data Protection 12.0, 12.1, and 12.2 allows a remote attacker to execute unauthorized SQL statements against the appliance, with the vendor-assessed 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 compromise of confidentiality, integrity, and availability of the affected component with no privileges or user interaction required. The vulnerable feature or endpoint is not publicly disclosed, so defenders cannot pin down a specific setting to harden, but the practical gating factor is reachability: Guardium is a data-security management appliance that normally sits on an internal or management network segment rather than the public internet. No public exploit code has been identified at time of analysis and there is no CISA KEV listing, but a vendor patch is available and should be treated as high priority because of the 9.8 severity and the sensitivity of the data Guardium manages.
Remote code execution in IBM Guardium Data Protection 12.0, 12.1, and 12.2 is enabled by a buffer overflow that an unauthenticated network attacker can trigger without user interaction, consistent with the assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H and a base score of 9.8, giving total loss of confidentiality, integrity, and availability on a successful exploit. No public exploit code has been identified at time of analysis, CISA's SSVC assessment records no observed exploitation with non-automatable attack steps, and EPSS places exploitation likelihood at 0.37% (29th percentile), so signals are mixed and point to a credible-but-not-yet-urgent priority. The practical limiting factor is network reachability: Guardium is typically deployed as an internal database-activity-monitoring appliance, so an attacker generally needs a foothold on, or routing into, the management or database-monitoring network rather than open internet access.
IBM Guardium Data Protection 12.1 and 12.2.2 contain a path traversal flaw (CWE-22) that lets a remote, unauthenticated attacker delete arbitrary files on the appliance by supplying traversal-laden input to an affected file-handling function, giving a high-integrity and availability impact with no confidentiality exposure (CVSS 3.1: 9.1, AV:N/AC:L/PR:N/UI:N/C:N/I:H/A:H). No public exploit code has been identified at time of analysis, EPSS is low at 0.36% (28th percentile), and CISA's SSVC decision framework rates exploitation as 'none' with a total technical impact, so this reads as a serious but not emergency-priority issue. Practical risk is bounded by reachability: Guardium is a management-plane appliance normally confined to privileged database and security administrators behind the enterprise perimeter, which narrows the realistic attacker population despite the network-vector rating.
SQL injection in IBM Guardium Data Protection 12.0, 12.1, and 12.2 lets remote unauthenticated attackers who can reach the product's network-facing interfaces inject crafted SQL against the back-end database, potentially viewing, adding, modifying, or deleting its contents (CVSS 3.1 base 9.8, vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). No public exploit code has been identified at time of analysis, and EPSS is low at 0.27% (17th percentile), so real-world exploitation appears opportunistic rather than widespread despite the maximum severity rating. Impact is exposure-dependent: internet-reachable or broadly accessible management/collector instances carry the full unauthenticated risk, while deployments confined to isolated management networks are substantially less exposed. The vendor has published remediation through IBM Support.
Man-in-the-middle interception of TLS-protected communications in IBM Guardium Data Protection 12.2.2 is possible because the product does not properly validate certificates (CWE-295), allowing an attacker positioned on the network path to read and modify traffic that the software treats as trusted. The flaw is unauthenticated (CVSS 3.1 AV:N/AC:H/PR:N/UI:N) but not trivially automatable, since the attacker must first achieve an active interception position - the reason CISA SSVC rates exploitation as none and automatable as no, and the reason the assessed impact is limited to confidentiality and integrity (C:H/I:H/A:N) rather than availability. EPSS is very low at 0.14% (3rd percentile), no public exploit code has been identified, and the issue does not appear in CISA KEV; IBM has released a vendor patch, so the practical risk for most deployments is remediation-tracking rather than emergency response.
Remote code execution in IBM Guardium Data Protection 12.0, 12.1, and 12.2 is possible through a stack-based buffer overflow (CWE-121) in reachable product code, with the vendor CVSS vector indicating a network-accessible, unauthenticated trigger and no required user interaction (AV:N/PR:N/UI:N) and a maximum impact rating of 9.8. Our independent assessment scores the same impact but raises attack complexity to High (AC:H), reflecting that reliable code execution likely requires an attacker to defeat standard memory protections such as stack canaries, ASLR, and DEP, and CISA's SSVC framework rates the issue non-automatable with no observed exploitation; no public exploit identified at time of analysis, and EPSS is low at 0.37% (29th percentile). The practical picture is a high-severity, patch-priority issue rather than an emergency: the vulnerable code is assumed reachable in standard deployments since the advisory names no special prerequisite, but exposure is confined to environments running the three named 12.x releases and the vendor fix closes the window once applied.
OS command injection in IBM Guardium Data Protection 12.2.2 and 12.1 lets a remote attacker execute arbitrary operating-system commands with the privileges of the vulnerable service, yielding a full compromise of confidentiality, integrity, and availability (CVSS 9.8, CWE-78). The CVSS vector rates the flaw as unauthenticated (PR:N) over the network (AV:N) with no user interaction, although IBM's own text does not confirm whether a valid console or API session is needed to reach the vulnerable command path, and the practical risk is narrowed by the fact that Guardium appliances are normally deployed on internal management networks rather than being internet-facing. As of analysis, there is no public exploit code identified, EPSS is low at 0.36% (28th percentile), CISA SSVC records Exploitation: none with Automatable: no, and there is no KEV listing, so the dominant driver of urgency is the severity of impact if an attacker does obtain a path to the interface rather than observed exploitation.
Crafted TDS PRELOGIN packets traversing a network segment monitored by an IBM Guardium Data Protection 12.0, 12.1, or 12.2 Collector trigger a buffer overrun in the appliance's Microsoft SQL Server protocol decoder, reliably causing denial of service and, per the vendor, potentially allowing arbitrary code execution on the Collector itself. Exploitation is unauthenticated (CVSS vector PR:N) and requires no user interaction, but it depends on the attacker's ability to place a malformed packet onto the monitored database network rather than reaching a directly addressable service, because the Collector inspects traffic passively. No public exploit code has been identified at time of analysis and EPSS is low at 0.36% (28th percentile); IBM has published a vendor fix, and CISA's SSVC assessment records no observed exploitation.
Remote code execution in IBM Guardium Data Protection 12.0, 12.1, and 12.2 allows unauthenticated network attackers to trigger a buffer overflow and execute arbitrary code, with total confidentiality, integrity, and availability impact as assessed by CVSS 3.1 base 9.8 (AV:N/AC:L/PR:N/UI:N). No public exploit code or active exploitation has been identified at time of analysis; EPSS is low (0.37%, 29th percentile), and CISA SSVC marks the attack as not automatable, meaning exploitation would likely require target-specific effort. A vendor patch is available per IBM advisory node/7291674.
SQL injection in IBM Guardium Data Protection 12.1 and 12.2.2 allows unauthenticated remote attackers to execute arbitrary SQL commands against the platform's underlying data store, with IBM's own vector (AV:N/AC:L/PR:N/UI:N, C/I/A:H) describing total loss of confidentiality, integrity, and availability for exposed instances. The headline 9.8 CVSS should be tempered by conflicting signals: EPSS is only 0.30% (20th percentile), and CISA's SSVC assessment records exploitation as 'none' with the attack rated non-automatable, with no public exploit code or KEV listing identified at time of analysis. Real-world risk is governed by reachability - exploitation requires network access to a vulnerable Guardium management or collector interface, which is normally confined to restricted internal management networks rather than the internet.
Remote code execution in IBM Guardium Data Protection 12.0, 12.1, and 12.2 is achievable by an unauthenticated remote attacker (CVSS PR:N, UI:N) through a buffer overflow that corrupts memory in a way that can be leveraged to run arbitrary code, yielding high confidentiality, integrity, and availability impact (CVSS 8.1). Attack complexity is High (AC:H), so reliable exploitation depends on conditions outside the attacker's control - such as precise memory layout, timing, or a specific non-trivial input path - which tempers the practical risk despite the elevated base score. Only the listed 12.x branches are affected and patched builds are not exploitable; no public exploit code has been identified at time of analysis and there is no CISA KEV confirmation of active exploitation.
Missing authentication on a critical management function in IBM Guardium Data Protection 12.2 and 12.2.2 allows unauthenticated remote attackers to invoke arbitrary management operations against the affected appliance, with the highest possible impact to confidentiality, integrity, and availability (CVSS 9.8, AV:N/AC:L/PR:N/UI:N). Because the CVSS vector specifies PR:N with no user interaction and no non-default configuration prerequisite, any network-reachable management interface or API endpoint on an affected version is potentially exploitable without credentials; the practical constraint is reachability, since Guardium management planes are typically confined to internal or dedicated management segments. At time of analysis there is no CISA KEV entry and no publicly available exploit code identified, so exploitation is assessed as technically straightforward but not yet observed in external telemetry.
Remote code execution is possible in IBM Guardium Data Protection 12.0, 12.1, and 12.2 through a buffer overflow (CWE-119) triggered over the network, but exploitation requires valid low-privileged credentials (CVSS 3.1 AV:N/AC:L/PR:L/UI:N, base 8.8) - this is not an unauthenticated flaw, so an attacker must already hold an account or captured credential on the appliance. A successful exploit yields full compromise of confidentiality, integrity, and availability of the affected system, making privileged accounts and network reachability the key gating factors. Exploitation status is benign-to-moderate: no public exploit code has been identified and no confirmed in-the-wild activity is reported (EPSS 0.42%, 34th percentile; CISA SSVC exploitation: none), and IBM has published an advisory with a vendor fix, so patching is the decisive control.
IBM Guardium Data Protection 12.0, 12.1, and 12.2 ship with hard-coded credentials that a remote, unauthenticated attacker (CVSS PR:N/UI:N) can abuse to read sensitive information from the affected appliance service, yielding a high confidentiality impact with no integrity or availability loss (C:H/I:N/A:N, base 7.5). Exploitation is not trivial in practice: the attacker must first know or recover the static credential value and must be able to reach the Guardium management or data service over the network, which is typically an internal, segmented appliance rather than an internet-facing endpoint. There is no confirmed active exploitation (not in CISA KEV), no public exploit code identified at time of analysis, and EPSS is only 0.30% (21st percentile), so this rates as a genuine but moderate-priority exposure that should be scheduled rather than emergency-patched.
Information disclosure in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 (including the Security Verify Access Container and Verify Identity Access Container editions) allows unauthenticated remote attackers to read sensitive data from a network-reachable instance, per the CVSS vector AV:N/AC:L/PR:N/UI:N with confidentiality impact rated High and no integrity or availability effect. No public exploit code has been identified and CISA's SSVC assessment records no observed exploitation, with the attack classified as not automatable and only partial technical impact, indicating targeted rather than mass-scannable abuse. Vendor-released fixes are available from IBM, so exposure is primarily a function of how reachable the identity appliance or container endpoints are from untrusted networks.
Improper authorization enforcement in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 can allow unauthenticated remote attackers (PR:N, UI:N) to bypass access controls and alter protected content or state (I:H, C:N, A:N) when the product is deployed in front of certain web servers. The flaw, however, is configuration-dependent: as reflected by the AV:N/AC:H vector and IBM's scoping to 'some' web servers, only specific protected web-server integrations are exposed, and default or unaffected setups are not exploitable. No public exploit code or confirmed active exploitation was identified at time of analysis, and IBM rates the issue 5.9 (moderate); the affected deployments also include the containerized editions of both products.
Authentication bypass in IBM Security Verify Access (10.0 through 10.0.9.2) and IBM Verify Identity Access (11.0 through 11.0.3), including their container editions, allows a remote, unauthenticated attacker to defeat security restrictions and gain unauthorized access to functionality that should be protected. With a CVSS 3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N, C:N/I:H/A:N), the flaw is network-reachable, low complexity, and requires no credentials or user interaction; the impact is rated as high on integrity, meaning an attacker can alter protected data or configuration through the bypass. The only practical precondition is that the affected authentication or management interface be reachable by the attacker. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (not listed in CISA KEV); a vendor patch is available per IBM advisory node 7291628.
Remote code execution is possible in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3, including the containerized editions of both products, because a protection mechanism fails to prevent an authenticated principal from influencing code execution paths. Successful exploitation requires only a valid low-privilege account and network access to the product interface (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 8.8) - no user interaction or race condition is needed - and yields full compromise of confidentiality, integrity and availability of the affected instance. At the time of analysis, no public exploit code has been identified for this CVE and there is no confirmed active exploitation, but the low attack complexity and the fact that the affected systems are identity and access management infrastructure make the issue a high-priority patching target; IBM has published a vendor remediation advisory.
Authenticated argument injection in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 (including the containerized editions) allows a remote attacker who already holds valid credentials to slip crafted parameters into command or process arguments and trigger unauthorized actions, with high impact to confidentiality, integrity, and availability (CVSS 8.8). Exploitation requires authenticated access (CVSS vector PR:L) and no user interaction (UI:N), so the exposed population is limited to existing platform users rather than anonymous internet traffic. No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited (no CISA KEV listing), but a vendor patch is available and the affected systems are typically high-value identity infrastructure, making prompt remediation worthwhile.
Authentication bypass in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 (including the container editions) allows a remote, unauthenticated attacker to defeat the product's authentication control entirely, with no user interaction required. The 7.5 CVSS score reflects a high integrity impact only - the vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N) assigns no confidentiality or availability impact - so the practical effect is that an attacker can perform authenticated actions with the privileges of a legitimate session while exposing no data directly. IBM has published a vendor fix via support node 7291628, and no public exploit code has been identified at time of analysis; this is a credible operational priority but not a confirmed emergency.
Unauthenticated remote attackers can render IBM Security Verify Access (10.0 through 10.0.9.2) and IBM Verify Identity Access (11.0 through 11.0.3), including their container editions, unavailable by driving the software into uncontrolled recursion - a stack-exhausting condition with availability-only impact (CVSS 3.1 7.5, AV:N/AC:L/PR:N/UI:N/C:N/I:N/A:H). Because the vector specifies PR:N/UI:N, no credentials, user interaction, or special configuration are prerequisites, so any network-reachable, unpatched instance is a candidate and exposure management is the primary limiting factor; attacks against non-internet-facing deployments placed behind rate-limiting proxies are substantially harder to sustain. No public exploit code has been identified at time of analysis, and CISA's SSVC assessment records Exploitation: none and Automatable: no with partial technical impact, so this should be treated as a high-availability-risk but not currently exploited issue.
Path traversal (CWE-22) in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 allows a remote, unauthenticated attacker to write arbitrary files on the affected appliance or container by supplying crafted path components. Per the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N, 7.5) exploitation is network-reachable, low-complexity and unauthenticated, with high integrity impact and no confirmed confidentiality or availability impact - a file-write primitive rather than a file-read or denial-of-service bug. No public exploit identified at time of analysis and the CVE is not listed in CISA KEV; the vendor has released a patch and the sole reference is IBM's advisory at https://www.ibm.com/support/pages/node/7291628. Exposure is bounded by network reachability: instances sitting behind reverse proxies or confined to internal/DMZ segments that attackers cannot reach are not directly exploitable.
Arbitrary command execution in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 (including their container images) allows a remote attacker holding a valid low-privilege account to run commands on the underlying system by slipping argument delimiters into data that is passed to a backend process without neutralization (CWE-88). The CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (8.8) means the attack is network-reachable with no user interaction and yields full loss of confidentiality, integrity, and availability, but exploitation is not possible fully unauthenticated - the attacker must already have credentials, which narrows the realistic threat to insiders, compromised low-privilege accounts, and post-compromise escalation. There is no public exploit identified at time of analysis, though the vendor has published a patch, so unpatched deployments within the affected ranges should be treated as exposed to any authenticated user.
Cross-site request forgery in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 (including their container editions) lets a remote attacker who lures a logged-in user into loading attacker-controlled content submit unauthorized, privileged state-changing requests through that victim's authenticated session; CVSS 3.1 rates it 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). The attacker needs no credentials of their own, but successful abuse depends on a concurrently authenticated victim - most damagingly an administrator - plus a social-engineering/user-interaction step, so exposure is greatest where the management interface is internet-reachable. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (CISA KEV); a vendor patch is available per IBM's advisory.
Unauthenticated remote code execution affects IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 - including their containerized editions - through deserialization of untrusted data, allowing an attacker who can reach the affected service to run arbitrary code on the system. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 9.8) confirms the flaw is network-reachable and requires no authentication, privileges, or user interaction, so any exposed, unpatched instance should be considered directly exploitable; the only real gating factors are running an affected build and whether the vulnerable endpoint is network-accessible. No public exploit code or confirmed active exploitation has been identified at time of analysis, but a vendor patch is available and the pre-authentication nature of the issue places it in the highest remediation priority tier.
Remote code execution is achievable in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3, including their container editions, because the affected services deserialize untrusted data received over the network. The flaw is reachable without authentication and without user interaction (CVSS 3.1 base 9.8, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), allowing an attacker who can reach the vulnerable endpoint to run arbitrary code with the privileges of the affected process. There is no public exploit identified at time of analysis and the issue is not confirmed as actively exploited (CISA KEV), but a vendor patch is available and the only practical barrier to exploitation is network reachability of the exposed service.
Arbitrary code execution is possible in IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 (including their container editions) when an attacker who already holds administrative privileges on the appliance and can reach the local management interface supplies input that overflows a fixed-size stack buffer. The assessed CVSS 3.1 base score is 7.2 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) with CWE-787 as the root cause, so the flaw is high-severity on impact but gated by a strong prerequisite: administrative control of the management plane rather than unauthenticated reach. Patch available per vendor advisory (IBM support page node/7291628); there is no CISA KEV entry and no public exploit code identified at time of analysis, and CISA SSVC decision points record Exploitation: none, Automatable: no, Technical Impact: partial.
An out-of-bounds read in the TDS7 LOGIN7 protocol parser of IBM Guardium Data Protection 12.0, 12.1, and 12.2 allows unauthenticated remote attackers to deliver a crafted LOGIN7 packet with invalid offset or length values, causing denial of service and limited memory disclosure. The published CVSS 3.1 score is 9.1, but our independent assessment reduces confidentiality to Low (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H), and with EPSS at only 0.29% (20th percentile), no CISA KEV listing, and no public exploit identified at time of analysis, real-world priority is lower than the headline score suggests even though technical impact is rated total. The dominant limiting factor is network reachability: only deployments whose TDS/database-interception listener is exposed to untrusted networks are practically at risk.
Remote, unauthenticated memory corruption in IBM Guardium Data Protection 12.0, 12.1, and 12.2 allows an attacker who can reach a monitored MongoDB data path to overflow a heap buffer in the product's MongoDB protocol parser and potentially crash the appliance or execute arbitrary code. The flaw is triggered by a MongoDB SCRAM authentication message carrying an oversized username field, and because the parser runs inside the inspection engine, exposure is limited to deployments where Guardium's S-TAP/collector is actively inspecting MongoDB traffic. The vendor-rated CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, 9.8) describes a pre-authentication, low-complexity flaw with full confidentiality, integrity, and availability impact, though no public exploit code has been identified at time of analysis and reliable code execution (as opposed to a denial-of-service crash) is constrained by heap-exploitation difficulty.
A heap-based buffer overflow in IBM Guardium Data Protection's S-TAP TrafficTap TDS login reassembly routine allows an unauthenticated remote attacker to crash the agent or potentially execute arbitrary code by sending crafted TDS login fragments that overflow the fixed-size reassembly buffer. Affected deployments are Guardium Data Protection (S-TAP agent) versions 12.0 and 12.1, with EUVD additionally listing 12.2; exploitation requires the S-TAP agent to be actively inspecting TDS traffic on a reachable database-communication path, so exposure is limited to networks where an attacker can inject traffic into monitored Microsoft SQL Server or Sybase/SAP ASE sessions. The vendor rates this CVSS 3.1 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), and no public exploit code or confirmed active exploitation was identified at time of analysis.
Local privilege escalation in Guardium Data Protection 12.2 allows an authenticated low-privileged local user to abuse the cp_wrapper component to gain root privileges and access or modify sensitive system files. The issue is not remotely exploitable (AV:L) and requires a pre-existing local foothold (PR:L), so it is most relevant to insider threats, compromised low-privileged accounts, and post-compromise escalation; no public exploit identified at time of analysis, and no CISA KEV confirmation was provided. IBM has released a vendor patch, and this is a credible but not emergency-tier priority.
Local privilege escalation in IBM Guardium Data Protection 12.2 allows an attacker who already holds low-privilege local access on the appliance to recover the root password through the pkcrypto passkey component and thereby obtain full root control, because that component combines weak cryptographic protection with a hard-coded recovery key (CWE-798). The exposure is confined to a local attack path (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning no network or unauthenticated remote vector exists and the attacker must first establish a foothold on the appliance - realistically an insider or someone who has already compromised the host by other means. There is no public exploit identified at time of analysis, CISA SSVC rates exploitation as none and the flaw as non-automatable while assigning total technical impact, and EPSS is 0.11% (1st percentile), so this is a serious but not urgent technical issue.
Local privilege escalation to root in the IBM Guardium Data Protection 12.2 patch installer, where a signature-verification bypass lets an attacker substitute a tampered or unsigned patch artifact that the installer then executes with root privileges. Exploitation requires local access to the appliance with at least low-level privileges (PR:L) and the ability to stage a malicious patch and win a timing window during installation; the assessed vector is AV:L/AC:H with a resulting base score of roughly 7.0, slightly below the vendor-published 7.8. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the vendor has published a patch; this is a credible but not emergency-tier priority given the local-only attack path, prerequisite foothold, and race-condition reliability constraints.
Missing authentication in the edge-controller component of IBM Guardium Data Protection 12.1 and 12.2.2 allows unauthenticated remote attackers to push and execute arbitrary container images, which in turn grants control over the managed edge clusters that component orchestrates. The flaw is rated 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) for the base case and was independently assessed with scope-changed impact (S:C), reflecting that compromise of the controller extends to the clusters it manages; no credentials, privileges, or user interaction are required against a reachable instance. No public exploit code has been identified at the time of analysis and the issue has not been confirmed as actively exploited (CISA KEV), so the practical risk is driven by network exposure of the edge-controller interface rather than by an observed campaign; a vendor patch is available from IBM.
Unauthenticated path traversal in IBM Guardium Data Protection 12.2 allows a remote attacker who can reach the GIM (Guardium Installation Manager) file-upload interface to escape the intended upload directory and write arbitrary files onto a Collector host. The assessed vector (AV:N/AC:L/PR:N/UI:N, integrity impact) confirms that no credentials or user interaction are required against that endpoint, so any 12.2 Collector whose GIM upload service is reachable is exposed until patched; the practical attack surface is driven almost entirely by network segmentation of GIM. No public exploit code has been identified at time of analysis, and exploitation has not been confirmed as active - impact is file-system write access on the Collector, scoring CVSS 7.5.
Denial of service in IBM Guardium Data Protection 12.2.2 allows an unauthenticated remote attacker with network reachability to the edge-controller gRPC service to terminate the edge-controller process by supplying malformed task data that trips an unchecked type assertion. The assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, score 7.5) confirms no authentication, no user interaction, and no special timing are required once the port is exposed, and impact is confined to availability - the process crashes unexpectedly with no data disclosure or modification. There is no public exploit identified at time of analysis and no confirmed active exploitation (the CVE is not in CISA KEV), so the practical exposure is governed by reachability: deployments that keep the edge-controller gRPC endpoint on isolated management networks are not exposed to arbitrary remote attackers, while internet- or broad-LAN-accessible instances are at meaningful disruption risk. The primary limiting factor is that the gRPC port must be reachable, making this a genuine but bounded-impact availability issue.
Local privilege escalation in IBM Guardium Data Protection 12.2 lets an already-authenticated, high-privileged user gain root-level command execution by feeding attacker-controlled arguments to the SUID-root ssh_config_wrapper component. Because the component runs with effective UID 0, successful argument injection converts a privileged-but-limited foothold into full root control of the appliance, with high impact to confidentiality, integrity, and availability. This is a moderate-severity escalation issue rather than a remote-takeover emergency: the attacker must already hold a high-privileged account and be able to invoke the vulnerable binary locally, and no public exploit code has been identified at time of analysis. A vendor patch is available, though the specific fixed build is not enumerated in the supplied data.
Unauthenticated remote code execution in IBM DataPower Gateway affects the 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2 release trains, where a heap-based buffer overflow caused by improper bounds checking lets an attacker who can reach the appliance's request-processing path corrupt heap memory and run arbitrary code with full confidentiality, integrity and availability impact. The flaw is rated CVSS v3.1 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), meaning no authentication or user interaction is required, and it is exploitable over the network. There is no public exploit identified at time of analysis and it is not confirmed actively exploited (no CISA KEV listing); IBM has published a vendor fix, and this is a genuine high-priority issue rather than an inflated high-CVSS score.
Unauthenticated remote attackers can trigger a memory-safety fault in IBM DataPower Gateway that crashes the affected service, producing a denial-of-service condition; the assessed CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H, score 8.2) confirms network reachability with no authentication, no user interaction, and no unusual configuration required, while availability impact is High and there is a limited Confidentiality impact from potential leakage of adjacent memory. Affected releases are 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2. This issue is not confirmed as actively exploited (no CISA KEV listing) and no public exploit code has been identified at time of analysis, but a vendor patch is available and the affected versions are frequently internet-facing, so prioritization should follow normal critical-exposure timelines rather than emergency response.
Security-restriction bypass in IBM DataPower Gateway 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2 allows a remote authenticated attacker to have forged or tampered cryptographic signatures accepted by the gateway, defeating the trust checks those signatures are meant to enforce. Per the assessed vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N, 8.1), the attacker must already hold valid low-privilege credentials and have network reachability to the gateway, but no user interaction is required, and successful exploitation yields high confidentiality and integrity impact with no availability effect. No public exploit code was identified at time of analysis, and the issue is not confirmed as actively exploited (CISA KEV); the primary limiting factor is the authentication prerequisite, which excludes fully unauthenticated external attackers.
Empty-password LDAP authentication bypass in IBM DataPower Gateway lets remote, unauthenticated attackers obtain administrative access to affected appliances by submitting a blank password that the LDAP authentication logic fails to reject. The flaw carries a CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and affects 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2; exploitation requires only that LDAP be configured for administrative/management authentication and that the authentication interface be network-reachable. At time of analysis there is no public exploit identified, but IBM has published a vendor fix, and the combination of network-only attack surface, no authentication prerequisite, and full confidentiality/integrity/availability impact warrants emergency-level prioritization in any environment using LDAP-backed management logins.
Denial of service in IBM DataPower Gateway 11.0.0.0 through 11.0.0.2 allows an attacker who already holds a valid low-privileged account to trigger improper memory allocation during key derivation, corrupting memory and rendering the gateway unavailable (CVSS 7.7, AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H). Because the vector requires PR:L, the flaw is not exploitable pre-authentication, and its scope-changed rating reflects that the availability impact can extend past the initially compromised security boundary; there is no confidentiality or integrity impact. Patch available per vendor advisory and no public exploit identified at time of analysis, so risk is concentrated in unpatched appliances where an attacker can obtain even limited authenticated access.
Unauthenticated remote attackers can trigger a use-after-free in IBM DataPower Gateway, resulting in a denial of service and potential disclosure of sensitive information held in freed memory. The flaw affects the 10.5.0 branch (10.5.0.0 through 10.5.0.22), the 10.6.0 branch (10.6.0.0 through 10.6.0.10), the 10.6CD/10.6.1 branch (10.6.1 through 10.6.6), and the 11.0.0 branch (11.0.0.0 through 11.0.0.2); the CVSS vector (AV:N/AC:L/PR:N/UI:N, C:H/I:N/A:H) rates it 9.1, but exploitation requires the gateway endpoint to be network-reachable and, as a memory-safety bug, reliable triggering typically depends on request sequencing and allocator/timing state. There is no public exploit identified at time of analysis, EPSS is low at 0.24% (14th percentile), and CISA's SSVC framework records exploitation as none and automatable as no - signals are therefore mixed between a high headline severity score and a low observed exploitation likelihood. A vendor patch is available per IBM's advisory.
Remote code execution in IBM DataPower Gateway (10.5.0.0-10.5.0.22, 10.6.0.0-10.6.0.10, 10.6.1-10.6.6, and 11.0.0.0-11.0.0.2) is caused by a heap-based buffer overflow that a remote attacker can trigger without authentication or user interaction, carrying a CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N) with total impact to confidentiality, integrity, and availability. Exploitation is not confirmed by any signal: no public exploit code has been identified at time of analysis, the issue is not listed in CISA KEV, SSVC reports Exploitation=none with Automatable=no, and EPSS is only 0.37% (29th percentile). The practical risk therefore hinges on whether affected DataPower builds are reachable from untrusted networks, since IBM has published a fix and the high base score reflects worst-case impact rather than observed attack activity.
XML external entity injection in IBM DataPower Gateway 10.5.0.0-10.5.0.22, 10.6.0.0-10.6.0.10, 10.6.1-10.6.6, and 11.0.0.0-11.0.0.2 lets remote, unauthenticated attackers who can reach an XML-accepting endpoint read files or internal resources from the gateway host and, via entity expansion, exhaust memory. The CVSS:3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L, base 8.2) confirms no credentials or user interaction are required, with high confidentiality impact and low availability impact. There is no public exploit code and no indication of active exploitation, and IBM has published a patch through its support portal.
Out-of-bounds memory handling in IBM DataPower Gateway (10.5.0.0 through 10.5.0.22, 10.6.1 through 10.6.6, 10.6.0.0 through 10.6.0.10, and 11.0.0.0 through 11.0.0.2) allows network attackers to trigger a buffer overflow that can disclose sensitive process memory or crash the appliance. Per the assessed vector (AV:N/AC:L/PR:N/UI:N), exploitation is unauthenticated and requires no user interaction, with high confidentiality and availability impact but no integrity impact - consistent with the CWE-125 out-of-bounds read classification rather than a write-based code-execution primitive. No public exploit code was identified at time of analysis, CISA SSVC records exploitation as 'none' and automation as 'no', and EPSS is low at 0.22% (12th percentile); note that the vendor's own 9.8 rating assumes full C/I/A impact, which this assessment does not corroborate. Patch available per vendor advisory (IBM support page node/7289775).
Authentication bypass in IBM DataPower Gateway lets remote, unauthenticated attackers forge JSON Web Signatures and present themselves as a trusted, already-verified identity on gateways that use JWS/JWT signature verification for access control. Affected releases are 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2; per the assessed CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N, base 7.5) exploitation requires no credentials or user interaction and the impact is integrity-only, meaning the payoff is forged trust and unauthorized access rather than direct data disclosure. No public exploit identified at time of analysis, EPSS is low at 0.20% (9th percentile), and the CISA SSVC assessment records exploitation as none with automation not feasible, so this is a genuine but moderate-priority issue rather than a top-tier emergency; vendor patches are nonetheless available.
A remotely reachable, unauthenticated out-of-bounds write (buffer overflow, CWE-787) in IBM DataPower Gateway can corrupt memory and potentially allow an attacker to fully compromise the affected appliance, as reflected in the assessed CVSS 3.1 score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). Affected firmware spans 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2, with the flaw reachable in the normal network-processing path since no authentication, user interaction, or special configuration is required. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation, though the unauthenticated network attack surface and memory-corruption impact make this a genuine high-priority issue for exposed deployments; IBM has published a vendor fix via its support advisory.
Cross-site scripting in the IBM DataPower Gateway 10.6.0 Web UI (builds 10.6.0.0 through 10.6.0.10) lets an unauthenticated attacker inject arbitrary JavaScript that executes in the browser of an operator who is already logged into the appliance management console, potentially leading to credential or session disclosure within that trusted session. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N, 9.3) confirms the attacker needs no credentials but the victim must interact with attacker-supplied content, so this is a lure-driven, high-impact issue rather than silent mass exploitation; no public exploit has been identified at time of analysis. A vendor patch is available, and only the 10.6.0.x range up to 10.6.0.10 is affected, so upgrading the fixed build removes exposure.
Arbitrary code execution in IBM DataPower Gateway is possible when a user with existing local access to the appliance supplies crafted oversized input to a component that performs improper bounds checking, allowing an out-of-bounds write and, potentially, execution of arbitrary code in the appliance's process context. Affected release trains are 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2; IBM has published a vendor fix, and no public exploit code was identified at time of analysis. Note that the vendor-assigned CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N, score 9.8) characterizes this as remotely exploitable without privileges, which is inconsistent with the description's requirement for a local user and with the independent assessment of AV:L/AC:L/PR:L/UI:N - the local-access prerequisite is the practical limiter on real-world risk, while the impact if triggered remains full confidentiality, integrity, and availability loss.
Stack-based buffer overflow in IBM DataPower Gateway firmware tracks 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2 allows an authenticated attacker holding administrative-level privileges to execute arbitrary code on the gateway. Exploitation is network reachable but gated by high attack complexity (AC:H), meaning the attacker depends on conditions they cannot fully control, such as a specific memory layout or parsing state, so a single deterministic trigger is not guaranteed; the assessed vector is CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H. There is no public exploit identified at time of analysis and the issue is not reported as confirmed actively exploited (CISA KEV); IBM has released patched builds via its support advisory.
Out-of-bounds write in IBM DataPower Gateway lets a remote, unauthenticated attacker corrupt memory and potentially execute arbitrary code on affected gateway builds (10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2), as reflected in the CVSS v3.1 vector AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H and a base score of 8.1. The PR:N/UI:N components mean no credentials or user interaction are required, so any network-reachable instance on an affected build is exposed, though the AC:H rating indicates exploitation depends on satisfying a non-trivial condition - most likely a specific input state, parsing path, or memory layout - to escalate the write beyond a crash into reliable code execution. Vendor patch data indicates a fix is available from IBM, and no public exploit code or confirmed active exploitation was identified at time of analysis; the EPSS score was not provided in the underlying intelligence, so no probabilistic exploitation estimate can be quoted.
Unauthenticated remote code execution affects IBM DataPower Gateway across multiple release streams - 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2 - stemming from an out-of-bounds write (CWE-787) that corrupts memory and can be leveraged to run attacker-controlled code. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, 9.8) confirms the flaw is reachable over the network with no authentication and no user interaction, making any internet- or partner-facing DataPower instance running an unpatched build a high-priority target. Exploitation status: no public exploit identified at time of analysis, and the issue is not listed in CISA KEV; patch available per vendor advisory (IBM support page node/7289775), with the specific fixed firmware builds published there.
IBM DataPower Gateway can be driven into a denial-of-service condition by a remote, unauthenticated attacker who supplies input that reaches a flawed sorting comparator, causing the comparator to violate strict-weak-ordering and triggering an out-of-bounds memory access (CWE-787) that can crash or destabilize the affected service. All builds in the 10.5.0.0-10.5.0.22, 10.6.0.0-10.6.0.10, 10.6.1-10.6.6, and 11.0.0.0-11.0.0.2 ranges are affected; the impact is confined to availability (CVSS 3.1 base 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) with no confidentiality or integrity effect and no privilege gain. At time of analysis there is no confirmed active exploitation (not in CISA KEV) and no public exploit code identified, and IBM has published a fix via its support advisory, so this should be treated as a patching-priority availability risk rather than an emergency.
Unauthenticated remote attackers can drive IBM DataPower Gateway into resource exhaustion and denial of service by sending crafted GraphQL queries that abuse improper memoization of fragment spreads. Affected releases are 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2, and per the CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H vector no authentication or user interaction is required once a reachable GraphQL-processing endpoint exists. Impact is confined to availability (no confidentiality or integrity loss), and there is no public exploit identified at time of analysis; exposure depends entirely on whether the gateway has been configured to accept and process GraphQL requests.
Heap-based buffer overflow (CWE-787) in IBM DataPower Gateway allows an unauthenticated remote attacker to crash the gateway and cause a denial of service. Affected builds are 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2; per the CVSS vector (AV:N/AC:L/PR:N/UI:N) no credentials or user interaction are required, so any attacker who can reach a listening interface and deliver a crafted request to the vulnerable parsing path can trigger the fault. The assessed impact is availability-only (A:H, C:N/I:N) rated 8.2 High; no public exploit code and no confirmed active exploitation were identified at time of analysis, and the practical risk is governed mainly by network exposure of the gateway's listening interfaces. This is a genuine but tier-two priority issue rather than an emergency, with patches available from IBM.
A type confusion flaw (CWE-843) in IBM DataPower Gateway lets a remote, unauthenticated attacker crash a reachable gateway service, producing a denial-of-service condition. Affected builds are 10.5.0.0 through 10.5.0.22, 10.6.1 through 10.6.6, 10.6.0.0 through 10.6.0.10, and 11.0.0.0 through 11.0.0.2; the assessed CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, base 7.5) confirms a network-reachable, low-complexity, unauthenticated trigger with availability-only impact. IBM has published a vendor fix via its support advisory, and no public exploit code has been identified at time of analysis (no CISA KEV listing).
Out-of-bounds write in IBM DataPower Gateway lets unauthenticated remote attackers corrupt process memory, resulting in disclosure of sensitive information and denial of service. Affected releases are 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2, with a CVSS 3.1 base score of 8.6 driven by high availability impact alongside limited confidentiality and integrity impact. No public exploit code has been identified at time of analysis, and IBM has made a fix available through its support advisory, so this is a credible operational priority rather than a confirmed emergency - exposure depends on whether the gateway's network listeners are reachable by the attacker.
IBM DataPower Gateway is vulnerable to a remote, unauthenticated denial of service (CVSS 3.1 base 7.5) in which a crafted request triggers an out-of-bounds read, degrading or crashing the affected gateway service. All supported firmware streams in the affected ranges are exposed: 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6 (the 10.6 CD stream), and 11.0.0.0 through 11.0.0.2. The vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) confirms exploitable over the network with no authentication, privileges, or user interaction, but restricts impact to availability - no confidentiality or integrity loss is assessed - so exploitation results in service disruption rather than compromise; there is no public exploit identified at time of analysis, and a vendor patch is available.
Denial of service in IBM DataPower Gateway affects releases 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2, where crafted network input reaching the vulnerable parsing path overflows a buffer and can crash the affected service. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), exploitation requires no authentication and no user interaction, so any internet- or partner-facing listener that processes malformed input is exposed; impact is availability-only - a crash/restart condition rather than data exposure or code execution. No public exploit code has been identified at time of analysis and the flaw is not listed as confirmed actively exploited (CISA KEV), so this is a genuine but bounded operational risk that depends primarily on whether affected listeners are reachable from untrusted networks.
Unauthenticated remote attackers can crash IBM DataPower Gateway by sending a crafted request that triggers a null pointer dereference, resulting in a denial of service that takes the affected service interface offline. All four maintained release trains are affected: 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N) no authentication, user interaction, or privileged position is needed - only network reachability to a vulnerable, unpatched gateway - and the sole impact is availability (C:N/I:N/A:H), with no data exposure or code execution. No public exploit code or confirmed active exploitation was identified at time of analysis, so this is a credible but bounded availability risk that is governed primarily by how exposed the gateway's service interfaces are to untrusted networks.
An out-of-bounds write in IBM DataPower Gateway (10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2) allows an unauthenticated remote attacker to corrupt gateway memory, most reliably causing a denial of service and potentially enabling partial confidentiality or integrity compromise. The flaw carries a CVSS 3.1 base score of 8.6 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H), and the vector's PR:N/UI:N components confirm no credentials or user interaction are required to reach the vulnerable code - the practical limiting factor is whether the attacker's network can reach a DataPower service listener. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the vendor has published a fix via IBM Support (node/7289775).
Remote, unauthenticated code execution is possible in IBM DataPower Gateway versions 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2, because an out-of-bounds write in the RFC2047 encoded-word parser can corrupt memory and be leveraged to run arbitrary code. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N, base 9.8) indicates the flaw is network-reachable with low complexity, requires no credentials and no user interaction, and carries full confidentiality, integrity, and availability impact, though exploitation depends on a reachable service or flow that passes attacker-controlled data through MIME encoded-word decoding. According to available intelligence there is no confirmed active exploitation (not listed in CISA KEV) and no public exploit code identified at time of analysis; the primary source is IBM's advisory at https://www.ibm.com/support/pages/node/7289775.
Security restriction bypass in IBM DataPower Gateway leaves the appliance's authorization logic exploitable by unauthenticated remote attackers, allowing them to reach functionality or data that should have required elevated privileges. Affected builds are 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2; the CVSS 3.1 vector (7.4, AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N) confirms the attack is network-reachable with no credentials and no user interaction, but the high attack-complexity component means some condition outside the attacker's control - such as a particular request sequence, timing, or policy/configuration state - must be satisfied first, and the gateway service must be network-reachable at all. IBM's own PSIRT reported the issue and no public exploit code or confirmed active exploitation has been identified at time of analysis; impact is scored high for confidentiality and integrity with no availability impact, so the practical risk is unauthorized read/modification of gateway-mediated data or configuration rather than denial of service.
A heap buffer underwrite in IBM DataPower Gateway allows unauthenticated remote attackers to crash the gateway service, producing a denial-of-service condition on affected appliances. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N), the flaw is reachable over the network with no privileges or user interaction required, and impact is confined to availability (C:N/I:N/A:H). Affected firmware spans 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2; no public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV.
Denial of service in IBM DataPower Gateway allows a remote, unauthenticated attacker to crash or degrade an affected gateway by sending crafted input that the product fails to validate correctly, resulting in an out-of-bounds write in memory. All four supported release trains are affected: 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, score 7.5) confirms the attack is launched over the network with no authentication and no user interaction, and that the sole impact is availability - there is no confidentiality or integrity loss, so the risk is bounded to service outage on gateways whose vulnerable interface is reachable from untrusted networks. No public exploit code has been identified at time of analysis, no EPSS score was supplied, and CISA KEV does not list this CVE.
Denial of service in IBM DataPower Gateway allows a remote, unauthenticated attacker to crash or exhaust the message-processing service by sending crafted messages whose length field is mishandled during memory reallocation. All firmware levels in the ranges 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2 are affected; the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, score 7.5) indicates no authentication, user interaction, or non-default configuration is needed, and the only impact is loss of availability. There is no confirmed active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis, but because exploitation only requires network reachability to the gateway's message interface, internet- or partner-facing appliances should be treated as the highest-priority remediation targets.
A heap buffer overflow in IBM DataPower Gateway (affected firmware levels 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2) allows remote attackers to crash the service and cause a denial of service; the CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates no authentication, privileges, or user interaction are required, so any reachable affected gateway is a candidate target. Impact is confined to availability - the vendor reports no confidentiality or integrity loss and no code execution. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (not in CISA KEV); this is a genuine availability risk but not a top-tier emergency, with practical exposure limited by how broadly the gateway's data-plane and management interfaces are reachable.
Unauthenticated remote attackers can exhaust system resources on IBM DataPower Gateway firmware releases 11.0.0.0 through 11.0.0.2, degrading or halting availability of the gateway's traffic and management services. The flaw is rated CVSS 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), meaning no credentials, user interaction, or special positioning are required once the affected interface is reachable, but impact is confined to availability - there is no data disclosure, tampering, or code execution component. No public exploit code has been identified and there is no confirmed active exploitation (not listed in CISA KEV); the practical risk is therefore a bounded denial-of-service exposure that is highest where DataPower interfaces are internet-facing or unsegmented, and much lower where they sit behind network controls and rate limiting.
Denial of service in IBM DataPower Gateway lets unauthenticated remote attackers send crafted network traffic that triggers an out-of-bounds write (CWE-787), degrading or halting the gateway's availability. The flaw affects version lines 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2, scoring CVSS 3.1 base 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) with availability-only impact. No public exploit code has been identified at time of analysis and there is no CISA KEV listing, but IBM has published a vendor fix, so internet-facing gateways should be treated as the highest-priority upgrade target.
Remote code execution affects IBM Langflow OSS versions 1.0.0 through 1.12.2, where improper access control lets an attacker with a valid low-privilege account execute arbitrary code on the server. The flaw is network-reachable with low attack complexity and no user interaction (CVSS 3.1: AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 8.8), but it is gated by the requirement to hold an authenticated account, so exposure is greatest where the platform offers open self-service registration, uses shared credentials, or is internet-facing without network restrictions. No public exploit code has been identified and the issue is not listed as confirmed actively exploited (CISA KEV) at time of analysis; exploitation status and patch availability should be re-checked against the IBM advisory.
Authenticated remote code execution affects IBM Langflow OSS 1.0.0 through 1.12.2, where improper control of code generation lets any account with at least low privileges (CVSS PR:L, AV:N, UI:N) cause attacker-supplied code to run server-side on the Langflow host, yielding high confidentiality, integrity, and availability impact (CVSS 8.8). Exploitation is not possible against a default install without valid credentials, and no public exploit code or confirmed active exploitation was identified at time of analysis. The practical exposure therefore concentrates on internet-reachable or multi-tenant instances that permit self-registration or host untrusted users; isolated, single-tenant, network-restricted deployments with trusted operators carry substantially lower risk.
Authenticated code injection in IBM Langflow OSS 1.0.0 through 1.12.2 lets any remote user holding a valid low-privileged account execute arbitrary code on the hosting server, with high impact to confidentiality, integrity, and availability (CVSS 8.8, PR:L, no user interaction required). The attack surface is the code path where special elements used in code are not properly neutralized (CWE-94), so deployments that allow untrusted or self-registered accounts to author and run flows are the most exposed, while instances with closed registration and no internet exposure are materially less at risk. No public exploit code has been identified at time of analysis, EPSS is only 0.58% (46th percentile), and CISA SSVC rates exploitation as 'none', making this a serious-but-not-emergency issue; a vendor patch is available per IBM's advisory.
Authenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.12.2 allows a low-privileged user to run arbitrary code because the platform improperly controls generation of executable code (CWE-94). Exploitation requires only a valid account on the instance (CVSS PR:L, AV:N, AC:L, UI:N), so an attacker who holds or obtains any credential able to create, import, or execute a flow/component that reaches the vulnerable code-generation path can achieve full confidentiality, integrity, and availability impact on the host. No public exploit code was identified at time of analysis, CISA's SSVC assessment records exploitation as "none", and EPSS is 0.58% (46th percentile), placing this as a genuinely serious but not emergency-tier issue whose real-world risk scales with how exposed the Langflow instance is and how freely low-privilege accounts are provisioned.
Remote code execution in IBM Langflow OSS versions 1.0.0 through 1.12.2 allows an authenticated attacker with flow-authoring privileges to inject and execute arbitrary code through Langflow's code-generation mechanism (CWE-94). The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) rates this as high severity (8.8), requiring network reachability, low privileges, and no user interaction; however, in typical deployments where flow creation or modification is broadly granted, the practical barrier may be lower than the PR:L metric implies. No public exploit code or CISA KEV entry has been identified at time of analysis, and EPSS is 0.61% (48th percentile); IBM has released a vendor patch.
Deserialization of untrusted cache data in IBM Langflow OSS 1.0.0 through 1.12.2 can execute attacker-controlled code with the privileges of the Langflow service process, but only for an attacker who has already obtained two things: the Langflow server secret and write access to the backing Redis instance used as the application cache. Because both prerequisites are effectively gated - the server secret is a trusted signing/trust value and Redis is normally bound to localhost or a private, authenticated network - this is not exploitable by an anonymous remote attacker against a default deployment, which is why the practical risk is lower than the 7.5 base score suggests. No public exploit code has been identified at time of analysis and the issue is not listed as confirmed actively exploited (CISA KEV).
Remote code execution can result in IBM Langflow OSS 1.0.0 through 1.12.2 through a dependency confusion weakness, where the product resolves an expected dependency from a public package registry instead of the intended trusted source. The CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates an unauthenticated remote attacker with no user interaction required, and the unpatched severity is rated 9.8; however, our independent assessment lowers the attack complexity to AC:H because successful exploitation depends on the attacker knowing or guessing the exact dependency name and on the victim's resolver preferring an attacker-published public package over the legitimate one, typically during an install, build, or import event rather than against a running service. There is no confirmed active exploitation (CISA KEV does not list this CVE), SSVC records Exploitation: none and Automatable: no, no public exploit code has been identified at time of analysis, and EPSS is only 0.68% (51st percentile), so the practical near-term risk is materially lower than the 9.8 headline suggests. A vendor patch is available per the IBM advisory.
Sensitive information disclosure in IBM Langflow OSS 1.0.0 through 1.12.2 allows a remote, low-privilege authenticated attacker to retrieve objects belonging to other users by manipulating a user-controlled identifier that the application fails to scope to the requesting principal (CWE-639, IDOR-style authorization bypass). The flaw is network-reachable with low attack complexity and no user interaction, but it is gated on the attacker already holding valid credentials for a low-privilege account (CVSS PR:L); the assessed impact is a high-confidentiality, read-only exposure with no demonstrated integrity or availability effect, so realistic risk concentrates in multi-user or multi-tenant Langflow deployments where a low-trust account can reach another tenant's or user's data. Patch available per vendor advisory (IBM support node 7290694); no public exploit identified at time of analysis.
Unauthenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.12.2 lets any attacker who can reach the service execute arbitrary operating system commands on the underlying host. Rated CVSS 3.1 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), the flaw requires no credentials, no user interaction, and no non-default configuration, so a default Langflow deployment exposed beyond localhost is directly exploitable. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV); IBM has published a vendor advisory with a fix, and practical risk is concentrated in self-hosted developer instances that are bound to reachable interfaces rather than being restricted to localhost or placed behind authentication and firewalling.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.12.2 lets a remote attacker who already holds a valid low-privilege session execute arbitrary code on the host by sending a crafted request that bypasses improper input validation. The flaw is network-reachable, low complexity, and requires no user interaction (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 8.8), so the authentication requirement is the main barrier; deployments with open or self-service sign-up, internet exposure, or multi-tenant use carry the highest risk. No public exploit code was identified at time of analysis and the issue is not confirmed as actively exploited (no CISA KEV listing); the vendor has released a fix.
Authenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.12.2 lets any holder of valid credentials - even a low-privileged one - submit or edit a flow that reaches the server-side code-generation and execution path, resulting in arbitrary OS command execution on the Langflow backend. IBM scores it 8.1 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N) and classifies the root cause as CWE-94 code injection; no public exploit code has been identified at time of analysis and there is no CISA KEV listing, so active exploitation is not confirmed. The decisive risk factor is deployment posture: internet-exposed or multi-tenant instances running with authentication disabled, default or shared credentials, or open self-registration collapse the PR:L barrier and behave like unauthenticated RCE targets.
Authenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.12.2 lets any user who can log in to the instance run arbitrary code on the host, because the platform fails to properly constrain attacker-supplied input before it reaches a code-execution path. 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), meaning low-complexity, network-reachable exploitation that requires only a low-privileged account but yields full confidentiality, integrity, and availability impact - no user interaction and no elevated privileges are needed. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation, but IBM has published a vendor advisory with a fix, so the practical exposure is greatest for organizations that expose Langflow to untrusted networks or provision accounts broadly.
Remote code execution in IBM Langflow OSS versions 1.0.0 through 1.12.2 allows an authenticated attacker to run arbitrary operating-system commands by supplying crafted input to a component that fails to neutralize special elements before passing them to an OS command or code-evaluation path (CWE-94). Per the assessed CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), exploitation requires a valid low-privilege authenticated session on the Langflow instance, needs no victim interaction, and yields full confidentiality, integrity, and availability impact on the affected host. No public exploit code was identified at time of analysis, and the issue is not confirmed as actively exploited (CISA KEV); the practical risk is concentrated on network-exposed Langflow servers that use weak, shared, or default credentials, since a compromised or low-privilege account is the only prerequisite.
Improper access control in the vertex result caching subsystem of IBM Langflow OSS 1.0.0 through 1.12.2 lets a remote authenticated attacker read sensitive cached data or inject malicious content into vertex results that other users then consume. The issue carries a CVSS 3.1 base score of 8.3 (High) under the vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L, meaning it is network-reachable with low complexity and requires only a low-privileged account, while yielding high confidentiality and integrity impact and low availability impact. No public exploit code has been identified at time of analysis and the flaw does not appear in CISA KEV; IBM has published a patch advisory (node/7290694), so exposure is limited to unpatched deployments and to attackers who already hold valid credentials on the instance.
Authenticated remote code execution affects IBM Langflow OSS versions 1.0.0 through 1.12.2, where an incomplete blocklist in the built-in code security scanner can be bypassed to execute arbitrary code on the server. Exploitation requires a valid low-privilege account (CVSS PR:L) and the ability to submit code evaluated by the scanner; unauthenticated attackers are not sufficient. No public exploit code has been identified at time of analysis and there is no CISA KEV listing, though the high CVSS base score of 8.8 and the multi-tenant exposure of typical Langflow deployments make the risk significant where untrusted users can register or be provisioned.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.12.2 lets an authenticated attacker escape the application's code execution sandbox and run arbitrary commands on the host. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N) confirms network reachability and a low-privileged authenticated session as the only precondition, with no user interaction required. No public exploit code has been identified at time of analysis and there is no CISA KEV entry, but the low complexity and high impact make this a genuine prioritization concern for internet-exposed or multi-tenant deployments.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.12.2 allows attackers to execute arbitrary code via improper control of code generation (CWE-94). The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 9.8) indicates remote, unauthenticated, low-complexity exploitation with full confidentiality, integrity, and availability impact, though the independent assessment notes the pre-auth condition is not independently confirmed by the description. A vendor patch is available, and no public exploit code has been identified at time of analysis; risk is highest for internet-exposed instances within the affected version range.
Local privilege escalation on IBM i 7.3, 7.4, 7.5, and 7.6 allows an attacker who already holds a valid low-privilege user profile to reassign ownership of arbitrary files by supplying an improperly validated file path. The flaw carries a CVSS 3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning exploitation requires local access and low-privilege authentication but no user interaction, and yields high confidentiality, integrity, and availability impact. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (CISA KEV); IBM has released a patch, so patched systems are not exploitable.
IBM DataStage on Cloud Pak for Data 5.4.0.0 contains a path traversal flaw in its archive extraction routine that lets a remote attacker with a valid authenticated account write files outside the intended destination directory and ultimately execute arbitrary code with the privileges of the affected service (CVSS 3.1 base 8.8, AV:N/AC:L/PR:L/UI:N/C:H/I:H/A:H). The root cause is CWE-22 improper limitation of a pathname to a restricted directory, commonly known as an archive 'zip-slip' condition, where crafted entries in an uploaded archive escape the extraction root. Authentication is mandatory, so this is not an unauthenticated flaw; no public exploit code and no confirmed active exploitation were identified at time of analysis, and the realistic risk is concentrated in enterprise Cloud Pak for Data deployments where the attacker already holds platform credentials or a foothold.