IBM
Monthly
Unauthenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.12.4 lets a remote attacker reach a public execution path and trigger Python component code that is already stored inside a publicly accessible workflow, so the code runs inside the server process under the workflow owner's runtime context. The attacker does not inject new code; the flaw is a trust-boundary bypass in which the public path, intended to run only server-trusted component code, instead executes owner-supplied stored components. The deployment shape is the limiting factor - an exposed instance must host at least one public flow embedding a Python component - and no public exploit code has been identified at time of analysis, although the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, 9.8) shows no authentication or user interaction is needed to invoke the path, and the priority decision is act_now.
IBM Langflow OSS 1.0.0 through 1.12.8 allows unauthenticated remote attackers to bypass security restrictions through improper authentication, with a CVSS 9.8 vector indicating high confidentiality, integrity, and availability impact and no privileges or user interaction required. The vendor has published a patch and the vuln.today priority is act_now, though no public exploit was identified at the time of analysis. Network exposure is the main practical limiter, since instances behind VPNs, authentication proxies, or localhost-only access are less reachable.
Server-side request forgery in IBM Langflow OSS 1.0.0 through 1.12.3 lets a remote authenticated attacker with valid credentials induce the server to make requests on their behalf and potentially obtain sensitive information. Exploitation requires a network-reachable instance and an authenticated session (CVSS PR:L), with no user interaction; the changed scope indicates the server may reach systems the attacker cannot directly access, but the impact is limited to confidentiality. No public exploit was identified at time of analysis, and a vendor patch is available.
Remote authenticated SQL command execution affects IBM Langflow OSS 1.0.0 through 1.12.3: an attacker holding a valid account can abuse improper access control to run arbitrary SQL, with high confidentiality and integrity impact. Authentication requirements (CVSS PR:L) narrow exposure to instances with multiple, shared, or untrusted users, and the vendor has published a patch; no public exploit was identified at time of analysis, and CISA SSVC reports no known exploitation.
Remote authenticated code execution in IBM Langflow OSS 1.0.0 through 1.12.3 allows a low-privilege user to run arbitrary code because special elements used in code are not properly neutralized. The CVSS 3.1 score is 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), so the main constraints are an authenticated account and network reachability, while the exact vulnerable feature or input path is not described in the available sources. It is a genuine priority-tier issue, though short of an emergency; IBM reports a vendor patch, and no public exploit was identified at the time of analysis.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.12.3 is reachable by an attacker who can reach the deployment's message broker and deliver a malicious serialized message that Langflow then deserializes. The vendor-rated vector is CVSS 9.8 (AV:N/AC:L/PR:N/UI:N with high confidentiality, integrity and availability impact), and vuln.today's Decision label is act_now with a vendor patch already available. No public exploit has been identified at time of analysis, and CISA's SSVC assessment records exploitation as none and automatable as no while rating technical impact as total; in practice the exposure is bounded by whether the message broker is reachable from an attacker's network position.
Deserialization of untrusted data (CWE-502) in IBM Langflow OSS 1.0.0 through 1.12.3 allows a remote attacker who holds valid low-privilege credentials to execute arbitrary code on the instance, with high impact to confidentiality, integrity and availability (CVSS 3.1 base 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The authentication prerequisite is the main constraint on exposure: self-registered, multi-tenant or compromised accounts on a network-reachable Langflow deployment are sufficient, and no user interaction or special complexity is required. There is no KEV entry and no public exploit identified at time of analysis; IBM has published a vendor patch reference, and the issue is rated for remediation this week rather than as an emergency.
Remote authenticated OS command execution in IBM Langflow OSS 1.0.0 through 1.12.3 allows a user with a valid account to run arbitrary commands on a network-reachable instance, with CVSS 3.1 score 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Exploitation requires authentication and is low complexity, and no user interaction is needed. A vendor patch is available, and no public exploit identified at time of analysis; the available decision signal makes this a near-term remediation priority.
IBM Langflow OSS 1.0.0 through 1.12.3 exposes a remote, unauthenticated code execution path because special elements used in an OS command are not properly neutralized; CVSS 3.1 scores the issue 9.8 with high confidentiality, integrity, and availability impact. The vendor has released a patch, the issue is assessed as act_now, and no public exploit identified at time of analysis.
OS command injection in IBM Langflow OSS 1.0.0 through 1.12.4 allows a remote, authenticated attacker with low privileges to execute arbitrary OS commands, resulting in high confidentiality, integrity, and availability impact. The vendor has released a patch, and no public exploit identified at time of analysis. The supplied intelligence prioritizes remediation this week rather than treating it as a drop-everything emergency.
IBM Langflow OSS 1.0.0 through 1.12.4 contains a missing authorization check (CWE-862) that allows a remote authenticated low-privileged user to execute arbitrary code, with high confidentiality, integrity, and availability impact. The CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H makes valid low-privileged access the key prerequisite rather than unauthenticated reachability. No public exploit was identified at time of analysis, SSVC records exploitation as none, and a patch is available from IBM; this is a credible, high-priority vulnerability but not an emergency.
Authenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.12.4 is caused by improper neutralization of code in eval/exec, allowing a low-privileged attacker with a valid session to execute arbitrary code with high confidentiality and integrity impact (CVSS 8.8). IBM has released a vendor patch; no public exploit has been identified at time of analysis, and the main constraint is that the attacker must already hold authenticated access rather than being anonymous. The assessed risk is a genuine high-severity concern but not an emergency.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.12.4 lets a remote attacker who already holds a low-privileged authenticated account run arbitrary code on the host, via a code-generation pathway that is not properly controlled (CWE-94). Successful exploitation gives full confidentiality, integrity and availability impact to the Langflow instance; the authentication prerequisite (PR:L, no UI interaction) is the main limiting factor, so this is not an anonymous pre-authentication attack. No public exploit code or active exploitation has been identified at time of analysis (CISA SSVC exploitation: none, automatable: no), and IBM has published a vendor fix, making this a prompt-patch item rather than an emergency.
Unauthenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.12.8 allows a network attacker to execute arbitrary code on a reachable instance through improper control of code generation (CWE-94). With CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (9.8), no privileges or user interaction are required once the service is reachable; exposure is mainly limited by whether a Langflow deployment is network-accessible. IBM has released a vendor patch, the vuln.today priority is act_now, and no public exploit is identified at time of analysis.
Authenticated code injection in IBM Langflow OSS 1.0.0 through 1.12.8 allows a remote low-privileged account to drive the Agentic Assistant to generate or submit component code using patterns the product fails to block, leading to arbitrary operating system command execution on the server. Patch information is available from IBM, and no public exploit code was identified in the supplied intelligence at time of analysis; CISA KEV status and EPSS are not indicated.
Authenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.12.4 lets any holder of a low-privileged account configure a built-in code-execution component with attacker-supplied inputs, bypassing the administrator-only restriction and achieving arbitrary code execution with high confidentiality and integrity impact. Exploitation requires a valid low-privileged account and network access to the Langflow OSS instance, with no user interaction required; no public exploit identified at time of analysis. This is a genuine priority rather than a high-CVSS/low-risk artifact, given the low-privilege prerequisite and the availability of a vendor patch.
Sensitive information disclosure in IBM Langflow OSS 1.0.0 through 1.12.4 stems from improper authentication (CWE-287), allowing a remote attacker to reach protected functionality or data without proving identity and read information they should not have access to. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, base 7.5) confirms the flaw is network-reachable and requires no authentication or user interaction, with high confidentiality impact and no integrity or availability effect. No public exploit code or confirmed active exploitation has been identified at time of analysis, and the vendor has published a fix; exposure is limited to instances running an affected 1.0.0-1.12.4 release that are reachable by an attacker.
Authenticated remote command execution in IBM Langflow OSS 1.0.0 through 1.12.4 stems from improper control of code generation (CWE-94), allowing a low-privilege network attacker to run arbitrary commands on a reachable instance. IBM has a vendor patch available via its support advisory, no public exploit identified at time of analysis, and the current priority label is this_week. This is a serious, actionable issue for internet-exposed or multi-tenant deployments with open account provisioning, although the authentication requirement limits exposure for closed environments.
Local code injection in IBM Sterling Connect:Direct for Unix's apnotify utility can let an authenticated low-privileged user trigger a stack-based buffer overflow and potentially execute code with the host privileges of the utility. The flaw affects versions 6.4.0.0 through 6.4.0.6 and 6.3.0.0 through 6.3.0.7 and requires local access plus the ability to invoke apnotify with crafted input; there is no remote or unauthenticated path. No public exploit identified at time of analysis, and CISA KEV status is not indicated, so risk is concentrated on shared Unix hosts with untrusted local accounts.
IBM QRadar SIEM 7.6.0.0 through 7.6.0.4 and 7.5.0 through 7.5.0 Update Package 16 Interim Fix 001 contains an out-of-bounds read that a network-reachable attacker can trigger without authentication or user interaction. Successful exploitation can crash or degrade the service for a high availability impact and may expose limited adjacent memory, yielding low confidentiality impact; no public exploit has been identified at time of analysis and no KEV status is provided.
Unauthenticated remote resource exhaustion in IBM QRadar SIEM allows a network-reachable attacker to degrade or take down the security monitoring platform without credentials or user interaction, per the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N, availability-only impact). The vendor scored the issue 8.6 with Scope:Changed, while our independent assessment treats scope as unchanged (7.5-equivalent), since no downstream component beyond the QRadar service itself is demonstrated; either way the practical effect is loss of SIEM visibility while the attack runs. No public exploit code or confirmed active exploitation was identified at time of analysis, and the affected version range is not disclosed in the supplied data - it must be confirmed against IBM advisory node 7292244 before exposure decisions are made.
IBM App Connect Enterprise 13.0.1.0 through 13.0.8.2 can expose sensitive information because components of the product may bind to an unrestricted IP address (for example 0.0.0.0 or a public interface) rather than a loopback or otherwise restricted address, leaving the listener reachable from untrusted networks. IBM's published score is 9.8 CRITICAL (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), but the assessed vector is information disclosure only (C:H/I:N/A:N): a remote, unauthenticated attacker with network reachability to the exposed listener could read data they should not have access to, without user interaction or special conditions. The practical risk is entirely governed by network exposure - deployments that firewall ACE, segment it, or bind listeners to restricted interfaces are largely shielded; no public exploit code and no CISA KEV entry were identified at time of analysis.
Hard-coded cryptographic key in IBM Guardium Data Protection 12.1 and 12.2 means the same static key ships inside every installation, so an attacker who reverse-engineers the product and recovers that key can decrypt (and potentially forge) the data it protects across any deployment. The assessed vector (AV:N/AC:H/PR:N/UI:N) rates this High complexity rather than trivially exploitable, because the attacker must both extract the key and gain access to the ciphertext it guards, and the independent assessment scopes the realistic impact to confidentiality loss rather than integrity or availability. No public exploit code and no CISA KEV listing were identified at time of analysis, and no EPSS score was supplied; the issue is serious but not a top-tier emergency.
Unauthenticated remote write access in IBM DataStage on Cloud Pak for Data 5.4.0.0 lets an attacker manipulate the shared Redis backing store under any tenant's key, collapsing the platform's credential-encryption boundary and allowing cached flow parameters to be poisoned across tenants. The issue is rated CVSS 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N) and requires the multi-tenant deployment pattern where tenants share the same Redis instance. No public exploit was identified at time of analysis, and no CISA KEV entry was provided.
Stack-based buffer overflow (CWE-121) in IBM Planning Analytics 2.0 and 2.1 allows a remote attacker who holds valid low-privilege credentials to overflow an improperly bounds-checked stack buffer and potentially execute arbitrary code on the Planning Analytics server. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 8.8) confirms network reachability, low attack complexity, no user interaction, and high confidentiality, integrity and availability impact, with the credential requirement being the principal limiting factor rather than any technical obstacle. There is no CISA KEV listing and no public exploit code identified at time of analysis, so this is a high-priority patching item rather than an emergency, with exposure driven by how widely authenticated access is granted and whether the service is reachable from untrusted networks.
Hard-coded credentials in IBM Verify Identity Access 11.0.3.1 and IBM Security Verify Access 10.0.9.3 appliances can let an attacker in physical or adjacent-network proximity gain elevated privileges, with CVSS 3.1 score 8.8 reflecting high confidentiality, integrity, and availability impact. The CVSS vector indicates no privileges or user interaction are required (PR:N/UI:N), but the adjacent-network attack vector limits exposure to attackers who can reach the appliance locally or on an adjacent segment. No public exploit code or confirmed active exploitation was identified at time of analysis.
Remote code execution in IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 stems from an improper-authentication weakness (CWE-287) that lets a network-reachable, low-privilege authenticated attacker execute arbitrary code with no user interaction. The CVSS:3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 8.8) indicates full loss of confidentiality, integrity, and availability once the flaw is triggered. No public exploit code was identified at time of analysis, and the vulnerability has not been confirmed as actively exploited (CISA KEV); the primary constraint on attackers is the need for low-privilege authenticated access to the TRIRIGA platform.
Broken object-level authorization in IBM Langflow OSS 1.0.0 through 1.12.4 allows any authenticated low-privilege user to bulk-delete another user's messages, overwrite message content to inject malicious prompts, or reassign a conversation session ID to hijack the session. The CVSS 3.1 score is 8.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L), so exploitation requires a valid account and a shared deployment where other users' messages or sessions exist; single-user instances have little cross-user data to target. No public exploit code or confirmed active exploitation was identified at time of analysis, and this is assessed as above-average priority rather than an emergency.
Local privilege escalation in IBM Sterling Connect:Direct for UNIX (6.3.0.0-6.3.0.7 and 6.4.0.0-6.4.0.6) allows an authenticated local attacker with a low-privileged account to gain elevated privileges through improper privilege management. The CVSS 3.1 score is 8.4 (AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N), reflecting high confidentiality and integrity impact to the host with scope change, but the attack is not remotely reachable. No public exploit was identified at the time of analysis, and exploitation requires an existing local foothold on a host running the affected Connect:Direct components, likely under elevated privileges.
Stored cross-site scripting in IBM Cloud Pak System 2.3.6.0 and 2.3.6.1 allows an authenticated low-privileged user to save JavaScript payloads that execute in another user's browser when the affected page is viewed. The flaw is rated CVSS 7.4 (network-reachable, low privileges, scope change) and requires access to a web-console input field whose value is stored and rendered without proper sanitization or HTML encoding. No public exploit code was identified at time of analysis, and IBM has released a vendor patch.
IBM Concert versions 1.0 through 3.0.0 rely on weaker-than-expected cryptographic algorithms when protecting sensitive data, allowing an attacker who obtains that ciphertext - captured network traffic or exfiltrated at-rest data - to decrypt highly sensitive information. The weakness is confidentiality-only (C:H/I:N/A:N) with no authentication or user interaction required per the CVSS vector, though practical exploitation demands prior possession of the encrypted material and non-trivial cryptanalytic effort, which is why the independently assessed vector rates complexity as High rather than Low. No public exploit code or confirmed active exploitation was identified at time of analysis, and IBM has released a vendor patch.
Heap buffer overflow in IBM MQ Operator and IBM MQ Advanced Container Images lets an authenticated user with authority to perform MQPUT operations crash the queue manager or potentially execute arbitrary code by supplying malformed message options. The advisory is scoped to these containerized IBM MQ products, and exploitation requires valid MQ credentials plus put authority, so this is not an unauthenticated attack. No public exploit identified at time of analysis, and IBM has released a vendor patch.
Denial of service and potential remote code execution in IBM MQ deployments using the MQ Operator and MQ Advanced Container Images result from a heap buffer overflow when an authenticated attacker with put authority sends MQPUT or MQPUT1 operations carrying malformed message handle properties. The CVSS 8.8 vector is network-reachable and requires no user interaction, but the PR:L component means the attacker must already hold valid credentials and put permissions, so the practical threat is an insider or post-compromise actor rather than an unauthenticated remote attacker. No public exploit code was identified at time of analysis, and IBM has released a vendor patch.
Authenticated users of containerized IBM MQ deployments can cause denial of service or memory corruption by sending MQOPEN operations that are not properly validated for buffer size. The affected deployments identified in the CPE data are IBM MQ Operator and IBM MQ Advanced Container Images, with the provided feed using wildcard version fields rather than a precise version range. The vendor CVSS 3.1 score is 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), requiring valid MQ credentials and authority to open a queue or object; no public exploit was identified at time of analysis, and a vendor patch is available via IBM support advisory node 7292667.
Unrestricted Java deserialization in the MQ Classes for Java shipped with IBM MQ Operator (versions 2.0.0 through 4.0.4) and the long list of MQ Advanced container image builds (9.3.0.x, 9.4.x and 10.0.0.x) lets an authenticated low-privilege user trigger a denial of service against the queue manager and, if a usable gadget chain is present on the classpath, potentially execute arbitrary code. The flaw is rated CVSS 8.8 (AV:N/AC:L/PR:L/UI:N, high confidentiality, integrity and availability impact) and requires valid credentials but no user interaction; the specific interface that accepts the serialized stream is not described in the available sources. There is no evidence of active exploitation - the issue is not in CISA KEV, SSVC records exploitation as none and automatable as no, EPSS is only 0.29% (20th percentile), and no public exploit code has been identified at time of analysis; the vuln.today priority is this_week and IBM has published a vendor fix.
Remote code execution in IBM MQ Operator and IBM MQ Advanced container images is possible when a TLS-enabled channel processes a malformed TLS certificate whose distinguished name overflows a stack buffer during connection establishment. 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) because the certificate parsing happens before any authentication completes, so a remote attacker reaching a TLS listener on an affected queue manager needs no credentials and no user interaction; successful exploitation yields full compromise of confidentiality, integrity and availability. Exposure is bounded by configuration: only queue managers whose channels accept or require TLS (for example with SSLCIPH set) reach the vulnerable parsing path. A vendor patch is available, EPSS is low at 0.25% (15th percentile) and SSVC records exploitation as none with automatable no, so no public exploit code has been identified at time of analysis, but the priority label is act_now given total technical impact across a very broad set of shipped container image and operator versions.
Header-driven URI resolution in Apache Camel's HTTP producer components causes message-supplied CamelHttpUri and CamelRestHttpUri values to be expanded through CamelContext.resolvePropertyPlaceholders() before use, so an attacker who can influence those headers turns a URI string into a configuration-evaluation context and can read OS environment variables, JVM system properties, every registered secret-backend PropertiesFunction (AWS, Azure, GCP, HashiCorp, IBM, CyberArk, Kubernetes) and even invoke no-argument methods on beans in the registry. The flaw affects Apache Camel 4.0.0 before 4.18.5 and 4.19.0 before 4.22.1 across camel-http, camel-http-common, camel-vertx-http, camel-undertow and camel-netty-http, and a plain static to(http://backend/api) route is enough to be exposed; no authentication is required where a route is reachable by untrusted senders (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N, 8.2). Exploitation yields a high-confidentiality but limited-integrity impact, and while no public exploit code or CISA KEV entry exists at time of analysis, the preconditions are ordinary and the vendor has shipped fixes, so this warrants prioritised patching.
Local privilege escalation in IBM i 7.3, 7.4, 7.5, and 7.6 allows an authenticated, low-privileged user to obtain QSECOFR/Root authority, as described in CVE-2026-102917. The vulnerability has 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) and requires prior authentication and local access; it is not remotely exploitable. No public exploit code has been identified at time of analysis, and IBM has released a patch via its support advisory.
IBM WebSphere Application Server - Liberty (20.0.0.12 through 26.0.0.10) can be driven into a denial-of-service condition by a remote attacker whose request raises an uncaught exception, degrading availability with no confidentiality or integrity impact. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N), no authentication, privileges or user interaction are required - the only prerequisite is network reachability to an affected Liberty instance, and the exact endpoint or feature that triggers the fault is not described in the available sources. Exploitation has not been confirmed (CISA SSVC: Exploitation none) and no public exploit code has been identified; EPSS is low at 0.32% (23rd percentile), and the CISA SSVC assessment rates automation as possible but technical impact as partial, so prioritization within a weekly patch cycle is appropriate rather than emergency action.
Remote unauthenticated authorization bypass in IBM WebSphere Application Server Liberty 20.0.0.12 through 26.0.0.10 can let attackers reach resources or operations beyond their intended privileges, with high confidentiality and integrity impact and no availability impact. The defect is CWE-863 incorrect authorization, and the supplied sources do not describe the specific trigger, feature, or configuration involved. No public exploit identified at time of analysis; EPSS is 0.33% (24th percentile), while the vuln.today decision label is act_now and CISA SSVC records exploitation none with total technical impact.
Authentication bypass in IBM WebSphere Application Server - Liberty (17.0.0.3 through 26.0.0.10) allows remote, unauthenticated attackers to subvert the SAML 2.0 web single sign-on flow when the samlWeb-2.0 feature is explicitly enabled, resulting in a session fixation condition that yields high confidentiality and integrity impact with no availability impact (CVSS 3.1 base 9.1, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N). Because samlWeb-2.0 is an opt-in Liberty feature rather than a default, only deployments that have configured SAML SSO are in scope; in practice exploitation is most credible when a legitimate user subsequently authenticates through an attacker-influenced session, which is a practical limiting factor relative to the raw vector. There is no public exploit identified at time of analysis, no confirmed active exploitation (no CISA KEV listing), and no EPSS score was supplied with the available intelligence.
Unauthenticated remote attackers can corrupt the persisted status of batch job instances on IBM WebSphere Application Server - Liberty versions 17.0.0.3 through 26.0.0.10 via a deserialization flaw (CWE-502), rated CVSS 3.1 base 8.2 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L). Real-world exposure is limited because exploitation requires the optional, non-default Java Batch / JSR-352 batch management and persistence capability to be enabled on a network-reachable Liberty server, and the resulting impact is confined to the integrity of persisted batch state rather than full server compromise. No public exploit code has been identified and there is no confirmed active exploitation (no CISA KEV listing) at time of analysis.
Access control bypass in IBM WebSphere Application Server - Liberty 20.0.0.12 through 26.0.0.10 allows an unauthenticated remote attacker to call gRPC service methods while evading configured Liberty access controls. This is a genuine high-priority issue by multiple signals, with CVSS 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N), but practical impact is deployment-specific: it matters mainly where gRPC services are deployed and method-level access controls are relied upon. No public exploit identified at time of analysis and no CISA KEV confirmation was provided.
Insufficient isolation in WebSphere Liberty 17.0.0.3 through 26.0.0.10 allows an authenticated attacker who already has low-level privileges on one server instance to cross into other server instances that share the same installation, yielding high confidentiality and integrity impact with a changed scope (CVSS 8.2). Exploitation is conditional: it requires a shared or consolidated install topology and a pre-existing foothold on a co-located server, and the assessment rates this as a genuine but conditional priority rather than a mass-exploitation threat. No public exploit identified at time of analysis.
Denial of service in IBM WebSphere Application Server 8.5 and 9.0, and in IBM WebSphere Application Server - Liberty 17.0.0.3 through 26.0.0.10, allows remote unauthenticated attackers to disrupt availability by sending crafted serialized data to the product's messaging service. The root cause is insecure deserialization (CWE-502) in the messaging component, rated CVSS 3.1 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), so impact is confined to availability - confidentiality and integrity are not affected. Per the assessed vector, no credentials or user interaction are required once the messaging endpoint is reachable, but the vulnerable code path is only exercised where the messaging engine (SIB/JMS) is enabled and accepting input; environments that disable it or restrict it to trusted networks are materially less exposed. There is no public exploit identified at time of analysis, and this CVE is not listed as confirmed actively exploited (CISA KEV).
Cryptographic signature verification bypass in IBM WebSphere Application Server 8.5 and 9.0 and WebSphere Liberty 17.0.0.3 through 26.0.0.10 lets a remote, unauthenticated attacker forge or tamper with signed content that the server should reject, undermining trust in signed tokens and messages (CVSS 8.7, scope-changed integrity and confidentiality impact). Exploitation requires High attack complexity - the attacker must satisfy conditions outside their control when crafting input to reach the flawed verification path - so only deployments that process and validate signed input are realistically exposed. No public exploit identified at time of analysis, and the flaw is not listed in CISA KEV.
Improper authentication in IBM MCP Context Forge prior to 1.0.2 allows remote, unauthenticated attackers to forge HS256-signed JWTs using a JWT_SECRET_KEY shipped in mcpgateway/config.py and .env.example, gaining full platform-administrator access without a database account. The attack requires two conditions to hold simultaneously: the gateway must still use the known shipped signing key, and the platform-admin bootstrap must be active (REQUIRE_USER_IN_DB=false with the token subject set to PLATFORM_ADMIN_EMAIL); because the documented production default for REQUIRE_USER_IN_DB is true, strictly default production deployments are protected, as are operators who rotated the secret before upgrading. Where both conditions are met, forged administrator tokens survive password rotation, account deletion, and session revocation, enabling administrative disclosure, modification, and service disruption; no public exploit code has been identified at time of analysis and the issue is fixed in 1.0.2.
Improper authentication in the CSIv2 inbound propagation handler of IBM WebSphere Application Server 8.5 and 9.0 lets remote, unauthenticated attackers bypass authentication and have forged identity data accepted into the server-side security context, with high confidentiality and integrity impact (CVSS 3.1 base 8.1, AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H). Exploitation is not trivial - it requires network reachability to the CSIv2/IIOP inbound path and a deployment that actually relies on CSIv2 inbound identity propagation, which is what the AC:H metric reflects - and no public exploit identified at time of analysis. IBM has published a vendor fix, so this is best treated as a genuine high-priority issue rather than a drop-everything emergency, with prioritization going to internet- or partner-exposed CSIv2 listeners.
Authorization bypass in IBM WebSphere Application Server 8.5 and 9.0 lets an authenticated, low-privileged user who can reach the cell's management/communication network impersonate an administrator across the entire cell. Because exploitation requires both valid credentials (CVSS PR:L, authenticated) and adjacent-network positioning (CVSS AV:A) rather than open-internet reach, this is a credible mid-to-high priority issue rather than an emergency, although a successful attack yields high confidentiality, integrity, and availability impact. No public exploit code has been identified at time of analysis, and a vendor patch is available per IBM's advisory.
Unauthenticated remote denial of service affecting IBM WebSphere Application Server Liberty (17.0.0.3 through 26.0.0.10) and traditional IBM WebSphere Application Server 8.5 and 9.0, where uncontrolled resource consumption lets a network-reachable attacker degrade or exhaust server availability. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, base 7.5) confirms no authentication or user interaction is required and that impact is confined to availability, with no confidentiality or integrity loss. At the time of analysis no public exploit code has been identified for this issue, and CISA KEV does not list it as confirmed actively exploited; IBM has published a vendor fix via its support advisory at https://www.ibm.com/support/pages/node/7292214.
Out-of-bounds reads in the IBM i File Server allow a remote authenticated attacker to crash or disrupt the service while also leaking portions of adjacent memory, affecting IBM i releases 7.3, 7.4, 7.5 and 7.6. Exploitation is not unauthenticated: the CVSS vector (AV:N/AC:L/PR:L/UI:N) confirms that valid low-privilege credentials and network reachability to the File Server are both required, with high confidentiality and availability impact but no integrity impact, and no user interaction. No public exploit code has been identified at time of analysis, EPSS is low at 0.41% (33rd percentile), CISA SSVC rates exploitation as none and the issue as not automatable, and a vendor patch is available, so this is a moderate-priority patching item rather than an emergency.
Remote code execution and sensitive-information disclosure in IBM i 7.3, 7.4, 7.5, and 7.6 stem from improper data sanitization by the HTTP Server Administration web application (CWE-94 code injection). An authenticated attacker with only low privileges who can reach that administration interface over the network can inject and execute arbitrary code or read sensitive data, with the scope change (S:C) driving Confidentiality, Integrity, and Availability impacts all High for a CVSS 3.1 base score of 9.9. Exploitation is not unauthenticated and is not possible against systems that do not run the HTTP Server Administration interface, or that expose it only to a trusted management network; no public exploit has been identified at time of analysis and there is no CISA KEV confirmation of active exploitation, though IBM has published a vendor patch.
Remote unauthenticated attackers can cause a denial of service in IBM Aspera Enterprise WebApps versions 1.0.0 through 1.0.6 by exhausting resources through uncontrolled resource consumption (CWE-400). The flaw is network-reachable with low complexity, requires no privileges or user interaction, and results in high availability impact, yielding a CVSS 3.1 base score of 7.5. No public exploit code has been identified at time of analysis, and IBM has released a patch.
Local privilege escalation in IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 stems from a misconfigured PATH environment variable (CWE-426) that lets a local attacker place a malicious executable in a directory searched before trusted system paths. Exploitation requires an existing low-privileged foothold on the host and a writable directory on the PATH, yielding high confidentiality, integrity and availability impact (CVSS 7.8, AV:L/PR:L/UI:N). No public exploit code and no confirmed active exploitation were identified at time of analysis; the vendor has published a fix.
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 contains an XML external entity (XXE) injection flaw that allows an authenticated attacker holding an elevated/privileged account to read sensitive information from the application server and, through the changed-scope condition in the CVSS vector, potentially from resources beyond the vulnerable component's own security boundary. Network access with low attack complexity and no user interaction is required, but the PR:H privilege requirement confines realistic exploitation to insiders or attackers who have already obtained privileged credentials, making this a moderate-priority issue rather than an emergency; no public exploit has been identified at time of analysis and the CVE is not listed in CISA KEV.
Session token disclosure in IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 allows a remote authenticated attacker to read session tokens that are rendered directly into HTML response bodies, which can enable session hijacking of whichever account owns the exposed token. The assessed vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, so exploitation requires a valid low-privileged account and the confirmed impact is loss of confidentiality, not direct integrity or availability damage; the practical severity depends on whether tokens belonging to higher-privileged users are exposed rather than only the attacker's own session, in which case impact is minimal. No public exploit code or confirmed active exploitation has been identified at time of analysis, and a vendor patch is available per the IBM advisory.
Authenticated remote code execution in IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 arises from improper validation of file paths inside archives the platform extracts, allowing an attacker with a valid account to write files to arbitrary locations and execute code under the privileges of the TRIRIGA service (CVSS 3.1: 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The attack is network-reachable with no user interaction and low complexity, but the PR:L vector gates it behind an existing authenticated session, confining realistic exploitation to insiders or attackers who have already obtained platform credentials. No public exploit identified at time of analysis, and IBM has published a vendor patch advisory covering the affected 5.0.0-5.0.8 range.
Authenticated low-privileged users on IBM Planning Analytics 2.0 and 2.1 can delete folders and applications belonging to other users because the platform enforces access control at the wrong functional level. The flaw carries a CVSS v3.1 score of 7.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H), with the risk driven almost entirely by the high availability impact of destroyed workspaces rather than by any data disclosure. No public exploit code has been identified at time of analysis, and exploitation requires a valid account on a network-reachable instance, making this most realistically an insider or compromised-credential threat.
Improper authentication in IBM Planning Analytics 2.0 and 2.1 allows an attacker who already holds valid low-privilege credentials to escalate to unauthorized administrative access over the network, with high impact to confidentiality, integrity, and availability (CVSS 3.1 base 8.8, CWE-288). Because the vector carries PR:L, the flaw is not reachable by a fully unauthenticated outsider: the attacker must first obtain ordinary authenticated access to the deployment, after which the alternate-path authentication weakness grants administrative control. No public exploit code has been identified at time of analysis and the issue is not listed as confirmed actively exploited (CISA KEV), but IBM has published a vendor patch, so the primary risk is unpatched, internet- or partner-reachable Planning Analytics installations where low-privilege accounts are widely distributed.
Authentication bypass and privilege escalation in IBM Planning Analytics 2.0 and 2.1 allow an unauthenticated remote attacker to reach functionality that should require credentials by abusing improperly validated sub-requests (CWE-288). Per the assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, exploitation needs only network reachability to the Planning Analytics application interface - no authentication, no user interaction, and no documented non-default configuration - yielding high confidentiality, integrity, and availability impact, which is why the score is 9.8. Signals conflict and must be weighed carefully: despite the severity and total technical impact under SSVC, EPSS is only 0.36% (28th percentile), CISA SSVC records Exploitation: none, and no public exploit code has been identified at time of analysis, so this should be treated as a serious but not yet observed threat. The vendor has released a fix, so exposure is concentrated in unpatched, internet- or partner-reachable deployments.
Arbitrary file write via path traversal in IBM Planning Analytics 2.0 and 2.1 allows remote unauthenticated attackers to write files to arbitrary locations on the server by submitting a crafted URL containing '/../' sequences. The vulnerability carries a CVSS 3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N), indicating high integrity impact but no confidentiality or availability impact. A vendor patch is available per IBM support node 7291604, and no public exploit identified at time of analysis.
Path traversal in IBM Planning Analytics 2.0 and 2.1 allows a remote attacker to read arbitrary files from the host and overwrite certain application files by supplying crafted file paths to the service. The CVSS 3.1 vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N, base 8.2) confirms network reachability, low attack complexity, no authentication requirement (PR:N), and no user interaction, with high confidentiality impact and limited integrity impact. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis; the vendor has released a fix referenced in the IBM advisory.
Authenticated remote code execution in IBM Planning Analytics 2.0 and 2.1 stems from a stack-based buffer overflow (CWE-121) that allows a remote attacker holding valid low-privilege credentials to corrupt stack memory and execute arbitrary code. IBM assigns a CVSS 3.1 base score of 8.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N), and the independent assessment raises the availability impact to High, indicating a successful exploit may also crash or destabilize the affected service. No public exploit code has been identified at time of analysis and the vulnerability is not listed in CISA KEV; vendor patches are available via IBM support node 7291604.
Denial of service in IBM DataStage on Cloud Pak for Data 5.4.0.0 can be triggered by a remote user who already holds valid platform credentials and supplies path traversal sequences to the product's file-handling logic, disrupting or halting the service. Exploitation requires an authenticated session with low privileges (CVSS vector PR:L) and no action by a victim, so the practical barrier is credential access rather than network reachability; availability is the realistic impact, with no evidence of code execution. A vendor patch is available via IBM support advisory node 7288649, and no public exploit code or confirmed active exploitation was identified at time of analysis.
Authenticated path traversal in IBM DataStage on Cloud Pak for Data 5.4.0.0 allows a remote attacker holding a valid platform account to bypass intended directory restrictions and execute arbitrary code. Exploitation requires only low-privileged credentials (CVSS PR:L), needs no user interaction, and is network-reachable with low complexity, which is why the vector scores 9.9 Critical with a scope change (S:C) reflecting impact that can extend beyond the vulnerable component. Despite the high score, the practical risk picture is more moderate: EPSS is only 0.49% (40th percentile), CISA SSVC rates exploitation as none with automatable set to no, there is no public exploit code identified at time of analysis and no KEV listing, and the vendor has published a patch, so remediation is available rather than dependent on compensating controls alone.
Remote OS command execution in IBM DataStage on Cloud Pak for Data 5.4.0.0 allows an authenticated attacker holding only low-privileged credentials to run arbitrary operating system commands on the underlying DataStage host, with high impact to confidentiality, integrity, and availability (CVSS 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The flaw is an OS command injection (CWE-78) in which specially crafted input is passed to a system command without proper neutralization, so no user interaction is required and a single crafted request over the network is sufficient once valid access is obtained. Exploitation is gated by the need for existing credentials on the instance, and there is no public exploit code identified at time of analysis; IBM has published a fix via support node 7288649.
Authenticated remote code execution in IBM DataStage on Cloud Pak for Data 5.4.0.0 allows an attacker who already holds valid low-privilege credentials (CVSS PR:L, AV:N, UI:N) to run arbitrary operating system commands on the underlying host, resulting in high confidentiality, integrity, and availability impact (CVSS 8.8). The root cause is improper neutralization of special elements used in an OS command (CWE-94), meaning user-supplied input reaches a shell command without adequate sanitization. No public exploit code has been identified at time of analysis and the flaw is not confirmed actively exploited (not in CISA KEV), but a vendor patch is available per IBM's advisory, so unpatched 5.4.0.0 deployments exposed to multi-tenant users or broadly provisioned accounts should be prioritized for upgrade.
Man-in-the-middle interception of IBM DataStage on Cloud Pak for Data 5.4.0.0 client sessions lets an attacker who presents a forged TLS certificate capture the IAM bearer Authorization header that the session adapter attaches automatically, granting full platform-scope tenant API access to read and manipulate the victim's DataStage projects, flows, assets, and pipeline definitions. The root cause is CWE-295 improper certificate validation in client-side SDK code running on the user's own machine, so exploitation requires an external network interceptor on the path between that machine and the Cloud Pak for Data platform - a co-tenant inside the shared cluster cannot exploit it - together with an active authenticated session that transmits a live token. CVSS 3.1 scores this 7.4 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N); no public exploit identified at time of analysis, and patch data indicates a fix is available from the vendor.
Unauthenticated network requests to IBM Maximo AI Service 9.1.0 and 9.2.0 can exhaust server resources and render the service unavailable, as described by CWE-400 uncontrolled resource consumption. Per the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, base 7.5), the flaw is network-reachable, low-complexity, and requires no credentials or user interaction, but its impact is confined to availability - there is no data disclosure, data modification, or code execution. IBM has published a vendor patch advisory (https://www.ibm.com/support/pages/node/7290473); no public exploit code and no confirmed active exploitation were identified at time of analysis, so the realistic risk is service downtime for internet- or network-exposed deployments rather than a breach.
Denial of service in IBM Maximo AI Service 9.1.0 and 9.2.0 SaaS allows remote unauthenticated attackers to trigger uncontrolled recursion in an exposed processing path, causing availability impact. The assessed vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, so no privileges or user interaction are required and only availability is affected; no public exploit identified at time of analysis. IBM has released a vendor patch via its support advisory for the identified service levels, and because the product is SaaS, IBM controls the deployed instance and its patching.
Remote code execution in IBM Maximo AI Service 9.1.0 and 9.2.0 lets an unauthenticated remote attacker execute arbitrary code on an affected deployment by abusing improper control of code generation (CWE-94). With 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), the flaw requires no authentication, no user interaction, and no special conditions beyond network reachability of the vulnerable instance. No public exploit code has been identified at time of analysis, and there is no KEV listing; IBM has published an advisory with a vendor fix, so the practical priority is identifying and patching internet- or network-exposed Maximo AI Service 9.1.0/9.2.0 instances.
Denial of service in IBM Maximo AI Service 9.1.0 and 9.2.0 allows unauthenticated remote attackers to terminate the host process by sending malformed frames that the service does not handle correctly. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, score 7.5) confirms that no credentials or user interaction are required, so the only practical gating factor is network reachability to the service endpoint; impact is confined to availability with no data disclosure or modification. No public exploit code has been identified at time of analysis, and the vendor has published a patch advisory.
Denial of service in the IBM Maximo Application Suite IoT Component (versions 9.0.0, 9.1.0, and 9.2.0) allows a remote, unauthenticated attacker to exhaust or crash the service by triggering uncontrolled recursion in its input parsing/processing logic. The flaw carries a CVSS 3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), meaning no credentials or user interaction are required against a network-reachable instance, but the impact is strictly availability - there is no confidentiality or integrity effect. At the time of analysis there is no public exploit identified, and the vendor has released a fix via its support portal.
Memory corruption in IBM Power Systems host firmware FW1060.00 through FW1060.81 lets an attacker who already holds authenticated, high-privileged service-level access to the Flexible Service Processor (FSP) write crafted configuration data that corrupts the host firmware boot stack during system IPL, with the compromise then propagating to the hypervisor loaded by that firmware and to the managed system. Because the flaw is reachable only from the local FSP interface (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H, base 8.2) and only fires on a (re)boot cycle rather than at runtime, the practical attack path is an insider or compromised FSP service account on the management plane rather than a remote network attacker, and no public exploit identified at time of analysis and no CISA KEV listing is associated with this CVE. Full confidentiality, integrity, and availability impact is scored against the managed system, with a scope change reflecting that the corruption begins in host firmware but affects the separately-managed hypervisor.
Authenticated attackers holding service-level credentials on the Flexible Service Processor (FSP) can read or modify arbitrary regions of Hostboot memory on IBM Power Systems firmware levels FW1060.00 through FW1060.81 by sending a specially crafted message over the service processor mailbox interface, corrupting the host firmware boot stack and the hypervisor it subsequently loads. The flaw is rated CVSS 8.2 (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H), with the scope-change rating reflecting that the FSP compromise crosses a boundary into host firmware and produces high confidentiality, integrity, and availability impact on the managed system. Exploitation is gated behind high-privilege service-processor access rather than network reach to the managed OS, and no public exploit code has been identified at time of analysis; no EPSS score was supplied, so it could not be factored into the risk picture.
Local code execution in IBM Power Systems firmware (FW1060.00 through FW1060.81) lets an attacker who already holds authenticated service-level access to the Flexible Service Processor (FSP) send a crafted service processor mailbox message that overflows host firmware runtime attribute storage, compromising the managed system's memory and hardware interfaces. The CVSS 3.1 vector AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H (base 8.2) is internally consistent with that description: the flaw is local, requires high-privilege service-plane credentials, needs no user interaction, and its scope change reflects a jump across the trust boundary from the service processor into the host firmware runtime with high confidentiality, integrity and availability impact. No public exploit code has been identified at time of analysis and there is no CISA KEV entry; IBM published the vendor advisory at https://www.ibm.com/support/pages/node/7290126.
Arbitrary code execution on the host system is possible in IBM Power Systems firmware versions FW1120.00 through FW1120.01, FW1110.00 through FW1110.31, and FW1060.00 through FW1060.81, due to a stack-based buffer overflow (CWE-121) in the host firmware boot process image validation path. An attacker with high-privileged service access to the service processor (PR:H, AV:L) can supply a maliciously crafted code update image to execute arbitrary code on the host system, resulting in full confidentiality, integrity, and availability impact (CVSS 3.1 base score 8.2, High). No public exploit has been identified at time of analysis, and exploitation requires local/service-level access and high privileges, substantially limiting real-world risk.
Arbitrary code execution in the host firmware runtime of IBM Power Systems is possible via the service processor mailbox interface, affecting firmware levels FW1060.00 through FW1060.81. An attacker with authenticated service-level access to the Flexible Service Processor (FSP) can send a crafted mailbox message that overflows host firmware runtime attribute storage (CWE-121), gaining full access to the managed system's memory and hardware interfaces. This is a high-severity local/management-plane issue (CVSS 8.2) requiring high privileges; no public exploit has been identified at time of analysis, and while it is not a mass-exploitation priority, isolation of the FSP network and limiting service accounts are recommended.
Authenticated local access to the IBM Power Systems service processor enables writing crafted host firmware configuration data that crashes the boot stack during system initialization, potentially corrupting memory in firmware versions FW1060.00 through FW1060.81. This stack-based buffer overflow (CWE-121) has a CVSS 3.1 score of 7.3, with limited integrity impact and high availability impact. Exploitation requires service-level credentials (PR:L) and local access to the management plane (AV:L); no public exploit code or active exploitation is identified at time of analysis.
Denial of service in IBM Maximo AI Service 9.1.0 and 9.2.0 lets remote, unauthenticated attackers disrupt the service through improper input validation (CWE-20), with impact limited to availability and no confidentiality or integrity loss. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, base 7.5) indicates the flaw is network reachable, low complexity, and requires no privileges or user interaction, so any deployment exposing the AI Service interface beyond trusted internal networks is at risk. No public exploit code has been identified at time of analysis and the CVE is not listed as confirmed actively exploited (CISA KEV); the practical risk is driven by exposure scope rather than observed attack activity.
Unauthenticated remote attackers can force the IoT Component of IBM Maximo Application Suite 9.0.0, 9.1.0, and 9.2.0 into an infinite parsing loop by submitting crafted input, hanging the parser and degrading or denying availability of the affected service. The flaw is rated CVSS 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), so per the vector no credentials or user interaction are required, but the impact is confined to availability with no data exposure or code execution; the practical exposure depends on whether the IoT parsing interface is reachable from the attacker's network position. There is no indication of confirmed active exploitation (CISA KEV) and no public exploit code identified at time of analysis, and our independent assessment rates this a moderate-priority availability issue rather than a top-tier emergency.
Code injection in the IBM Maximo Application Suite Location Service for Esri component (versions 9.0, 9.1 and 9.2) allows an attacker who already holds high-privilege control over the Kubernetes operator's configuration input - specifically the container image reference consumed from an operator template - to inject a code path that the operator then acts on, resulting in a scope-changing compromise of workloads beyond the operator's own authority (CVSS 3.1 8.7, AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N, CWE-94). The injected image reference can cause attacker-influenced containers to be deployed under the operator's service account, which is why the impact is rated high for confidentiality and integrity even though the attack is not reachable by an unauthenticated outsider against a default deployment. Exploitation is gated by PR:H - the adversary must be able to modify the Location Service for Esri operator's template or custom resource values - no user interaction is required, and there is no public exploit identified at time of analysis.
Command injection in the IBM Maximo Application Suite 'Location Service for Esri' component (versions 9.0, 9.1 and 9.2) allows a highly privileged attacker to execute arbitrary shell commands through a Kubernetes operator task, compromising confidentiality, integrity and availability beyond the component's own security boundary (CVSS 8.7). Exploitation is access-gated rather than trivial: the optional Esri location component must be deployed and enabled, and the attacker must already hold high privileges in the MAS environment (PR:H), but once those two conditions hold there is no user-interaction requirement and attack complexity is low, so injection is straightforward. No public exploit code and no confirmed active exploitation were identified at time of analysis.
Unintended outbound network egress in IBM Maximo Application Suite's optional Location Service for Esri Component (versions 9.0, 9.1, and 9.2) stems from a misconfigured Kubernetes NetworkPolicy that fails to restrict pod egress, allowing traffic to reach destinations the deployment intended to block. Rated CVSS 3.1 base 7.7, the score is driven mostly by the Scope change (S:C) and High confidentiality impact (C:H) rather than ease of attack; the vector (AV:N/AC:L/PR:L/UI:N) indicates remote exploitation at low complexity but with the attacker already holding a low-privileged foothold inside the environment, and no user interaction is needed. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV not listed), so this is best treated as a moderate-priority network-segmentation and data-exposure issue affecting clusters that rely on the shipped NetworkPolicy for egress control.
Improper access control in the Location Service for Esri component of IBM Maximo Application Suite 9.0, 9.1, and 9.2 allows an attacker who already holds high privileges on the underlying Kubernetes/OpenShift platform to abuse a schema-less Custom Resource Definition (CRD) and escalate to full read and write control over affected resources, since the CRD enforces no input validation and the component applies insufficient authorization checks. Exploitation requires authenticated high-privilege access (CVSS vector PR:H), no user interaction, and the optional Esri Location Service add-on to be deployed, so the barrier to entry is significant; the assessed vector is AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H for a base score of 7.2. No public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV), making this a moderate-priority, high-barrier issue rather than an urgent widespread threat - though successful abuse yields high confidentiality and integrity impact on the Maximo environment.
Path traversal in IBM Maximo Application Suite 8.10, 8.11, 9.0, 9.1 and 9.2 lets remote, unauthenticated attackers read arbitrary files from the server by sending crafted URL requests containing '../' sequences. The flaw carries a CVSS 3.1 score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), so impact is confined to confidentiality with no data modification or denial of service, and the independent assessment rates the overall signal as moderate and internally consistent rather than alarming. No public exploit code was identified at time of analysis and the CVE is not listed in CISA KEV; practical exposure depends mainly on internet reachability and on the OS-level file permissions of the account running the Maximo web process, since only files that account can read are disclosed.
Authenticated attackers with low privileges can escalate to elevated privileges on IBM i systems running Db2 Mirror for i 7.4, 7.5, or 7.6 by submitting a crafted request that bypasses additional authorization and input-validation checks, potentially allowing malicious code execution. This critical-severity (CVSS 9.9) privilege escalation affects standard deployments and requires a valid low-privilege account; no public exploit code or active exploitation has been identified at time of analysis, but a vendor patch is available.
Authenticated users of IBM Db2 11.5.0 through 11.5.9 and 12.1.0 through 12.1.5 for Linux, UNIX and Windows (including DB2 Connect Server) can obtain sensitive information they are not authorized to see by issuing the CREATE WRAPPER command, which is improperly authorized. The vulnerability is rated CVSS 3.1 7.7 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N), so it requires a remote attacker to already hold valid Db2 credentials and the privilege to invoke CREATE WRAPPER; there is no integrity or availability impact, making this primarily an insider or compromised-credential risk rather than an unauthenticated breach vector. No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited, but fixed code is available from IBM and should be applied, particularly in environments where federation features are enabled.
Privilege escalation in IBM Db2 LUW (versions 11.5.0 through 11.5.9 and 12.1.0 through 12.1.5 on Linux, UNIX and Windows, including Db2 Connect Server) lets a locally authenticated low-privilege user elevate to higher privileges through improper privilege management, with high impact to confidentiality, integrity and availability and a scope change that can affect resources beyond the vulnerable component. Exploitation is constrained: the attacker must already hold a local foothold on the host and valid low-privilege credentials (CVSS vector AV:L/PR:L/UI:N), so this is not reachable by a remote unauthenticated adversary and realistically affects insiders or attackers who have breached another service on the same host. There is no public exploit identified at time of analysis and the issue is not in CISA KEV; a vendor patch is available, making this a credible, actionable priority for exposed Db2 LUW estate rather than an emergency.
Privilege escalation in IBM Db2 11.5.0 through 11.5.9 and 12.1.0 through 12.1.5 allows a local low-privileged attacker to gain elevated privileges on the Db2 host when the db2locssh feature is enabled. The vulnerability is not remotely reachable and requires an existing local account, making it a post-foothold escalation vector rather than a remote entry point. No public exploit code has been identified at the time of analysis, and IBM has released patches; this is a credible operational priority for environments with db2locssh enabled, but not an emergency.
Unauthenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.12.4 lets a remote attacker reach a public execution path and trigger Python component code that is already stored inside a publicly accessible workflow, so the code runs inside the server process under the workflow owner's runtime context. The attacker does not inject new code; the flaw is a trust-boundary bypass in which the public path, intended to run only server-trusted component code, instead executes owner-supplied stored components. The deployment shape is the limiting factor - an exposed instance must host at least one public flow embedding a Python component - and no public exploit code has been identified at time of analysis, although the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, 9.8) shows no authentication or user interaction is needed to invoke the path, and the priority decision is act_now.
IBM Langflow OSS 1.0.0 through 1.12.8 allows unauthenticated remote attackers to bypass security restrictions through improper authentication, with a CVSS 9.8 vector indicating high confidentiality, integrity, and availability impact and no privileges or user interaction required. The vendor has published a patch and the vuln.today priority is act_now, though no public exploit was identified at the time of analysis. Network exposure is the main practical limiter, since instances behind VPNs, authentication proxies, or localhost-only access are less reachable.
Server-side request forgery in IBM Langflow OSS 1.0.0 through 1.12.3 lets a remote authenticated attacker with valid credentials induce the server to make requests on their behalf and potentially obtain sensitive information. Exploitation requires a network-reachable instance and an authenticated session (CVSS PR:L), with no user interaction; the changed scope indicates the server may reach systems the attacker cannot directly access, but the impact is limited to confidentiality. No public exploit was identified at time of analysis, and a vendor patch is available.
Remote authenticated SQL command execution affects IBM Langflow OSS 1.0.0 through 1.12.3: an attacker holding a valid account can abuse improper access control to run arbitrary SQL, with high confidentiality and integrity impact. Authentication requirements (CVSS PR:L) narrow exposure to instances with multiple, shared, or untrusted users, and the vendor has published a patch; no public exploit was identified at time of analysis, and CISA SSVC reports no known exploitation.
Remote authenticated code execution in IBM Langflow OSS 1.0.0 through 1.12.3 allows a low-privilege user to run arbitrary code because special elements used in code are not properly neutralized. The CVSS 3.1 score is 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), so the main constraints are an authenticated account and network reachability, while the exact vulnerable feature or input path is not described in the available sources. It is a genuine priority-tier issue, though short of an emergency; IBM reports a vendor patch, and no public exploit was identified at the time of analysis.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.12.3 is reachable by an attacker who can reach the deployment's message broker and deliver a malicious serialized message that Langflow then deserializes. The vendor-rated vector is CVSS 9.8 (AV:N/AC:L/PR:N/UI:N with high confidentiality, integrity and availability impact), and vuln.today's Decision label is act_now with a vendor patch already available. No public exploit has been identified at time of analysis, and CISA's SSVC assessment records exploitation as none and automatable as no while rating technical impact as total; in practice the exposure is bounded by whether the message broker is reachable from an attacker's network position.
Deserialization of untrusted data (CWE-502) in IBM Langflow OSS 1.0.0 through 1.12.3 allows a remote attacker who holds valid low-privilege credentials to execute arbitrary code on the instance, with high impact to confidentiality, integrity and availability (CVSS 3.1 base 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The authentication prerequisite is the main constraint on exposure: self-registered, multi-tenant or compromised accounts on a network-reachable Langflow deployment are sufficient, and no user interaction or special complexity is required. There is no KEV entry and no public exploit identified at time of analysis; IBM has published a vendor patch reference, and the issue is rated for remediation this week rather than as an emergency.
Remote authenticated OS command execution in IBM Langflow OSS 1.0.0 through 1.12.3 allows a user with a valid account to run arbitrary commands on a network-reachable instance, with CVSS 3.1 score 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Exploitation requires authentication and is low complexity, and no user interaction is needed. A vendor patch is available, and no public exploit identified at time of analysis; the available decision signal makes this a near-term remediation priority.
IBM Langflow OSS 1.0.0 through 1.12.3 exposes a remote, unauthenticated code execution path because special elements used in an OS command are not properly neutralized; CVSS 3.1 scores the issue 9.8 with high confidentiality, integrity, and availability impact. The vendor has released a patch, the issue is assessed as act_now, and no public exploit identified at time of analysis.
OS command injection in IBM Langflow OSS 1.0.0 through 1.12.4 allows a remote, authenticated attacker with low privileges to execute arbitrary OS commands, resulting in high confidentiality, integrity, and availability impact. The vendor has released a patch, and no public exploit identified at time of analysis. The supplied intelligence prioritizes remediation this week rather than treating it as a drop-everything emergency.
IBM Langflow OSS 1.0.0 through 1.12.4 contains a missing authorization check (CWE-862) that allows a remote authenticated low-privileged user to execute arbitrary code, with high confidentiality, integrity, and availability impact. The CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H makes valid low-privileged access the key prerequisite rather than unauthenticated reachability. No public exploit was identified at time of analysis, SSVC records exploitation as none, and a patch is available from IBM; this is a credible, high-priority vulnerability but not an emergency.
Authenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.12.4 is caused by improper neutralization of code in eval/exec, allowing a low-privileged attacker with a valid session to execute arbitrary code with high confidentiality and integrity impact (CVSS 8.8). IBM has released a vendor patch; no public exploit has been identified at time of analysis, and the main constraint is that the attacker must already hold authenticated access rather than being anonymous. The assessed risk is a genuine high-severity concern but not an emergency.
Remote code execution in IBM Langflow OSS 1.0.0 through 1.12.4 lets a remote attacker who already holds a low-privileged authenticated account run arbitrary code on the host, via a code-generation pathway that is not properly controlled (CWE-94). Successful exploitation gives full confidentiality, integrity and availability impact to the Langflow instance; the authentication prerequisite (PR:L, no UI interaction) is the main limiting factor, so this is not an anonymous pre-authentication attack. No public exploit code or active exploitation has been identified at time of analysis (CISA SSVC exploitation: none, automatable: no), and IBM has published a vendor fix, making this a prompt-patch item rather than an emergency.
Unauthenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.12.8 allows a network attacker to execute arbitrary code on a reachable instance through improper control of code generation (CWE-94). With CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (9.8), no privileges or user interaction are required once the service is reachable; exposure is mainly limited by whether a Langflow deployment is network-accessible. IBM has released a vendor patch, the vuln.today priority is act_now, and no public exploit is identified at time of analysis.
Authenticated code injection in IBM Langflow OSS 1.0.0 through 1.12.8 allows a remote low-privileged account to drive the Agentic Assistant to generate or submit component code using patterns the product fails to block, leading to arbitrary operating system command execution on the server. Patch information is available from IBM, and no public exploit code was identified in the supplied intelligence at time of analysis; CISA KEV status and EPSS are not indicated.
Authenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.12.4 lets any holder of a low-privileged account configure a built-in code-execution component with attacker-supplied inputs, bypassing the administrator-only restriction and achieving arbitrary code execution with high confidentiality and integrity impact. Exploitation requires a valid low-privileged account and network access to the Langflow OSS instance, with no user interaction required; no public exploit identified at time of analysis. This is a genuine priority rather than a high-CVSS/low-risk artifact, given the low-privilege prerequisite and the availability of a vendor patch.
Sensitive information disclosure in IBM Langflow OSS 1.0.0 through 1.12.4 stems from improper authentication (CWE-287), allowing a remote attacker to reach protected functionality or data without proving identity and read information they should not have access to. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, base 7.5) confirms the flaw is network-reachable and requires no authentication or user interaction, with high confidentiality impact and no integrity or availability effect. No public exploit code or confirmed active exploitation has been identified at time of analysis, and the vendor has published a fix; exposure is limited to instances running an affected 1.0.0-1.12.4 release that are reachable by an attacker.
Authenticated remote command execution in IBM Langflow OSS 1.0.0 through 1.12.4 stems from improper control of code generation (CWE-94), allowing a low-privilege network attacker to run arbitrary commands on a reachable instance. IBM has a vendor patch available via its support advisory, no public exploit identified at time of analysis, and the current priority label is this_week. This is a serious, actionable issue for internet-exposed or multi-tenant deployments with open account provisioning, although the authentication requirement limits exposure for closed environments.
Local code injection in IBM Sterling Connect:Direct for Unix's apnotify utility can let an authenticated low-privileged user trigger a stack-based buffer overflow and potentially execute code with the host privileges of the utility. The flaw affects versions 6.4.0.0 through 6.4.0.6 and 6.3.0.0 through 6.3.0.7 and requires local access plus the ability to invoke apnotify with crafted input; there is no remote or unauthenticated path. No public exploit identified at time of analysis, and CISA KEV status is not indicated, so risk is concentrated on shared Unix hosts with untrusted local accounts.
IBM QRadar SIEM 7.6.0.0 through 7.6.0.4 and 7.5.0 through 7.5.0 Update Package 16 Interim Fix 001 contains an out-of-bounds read that a network-reachable attacker can trigger without authentication or user interaction. Successful exploitation can crash or degrade the service for a high availability impact and may expose limited adjacent memory, yielding low confidentiality impact; no public exploit has been identified at time of analysis and no KEV status is provided.
Unauthenticated remote resource exhaustion in IBM QRadar SIEM allows a network-reachable attacker to degrade or take down the security monitoring platform without credentials or user interaction, per the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N, availability-only impact). The vendor scored the issue 8.6 with Scope:Changed, while our independent assessment treats scope as unchanged (7.5-equivalent), since no downstream component beyond the QRadar service itself is demonstrated; either way the practical effect is loss of SIEM visibility while the attack runs. No public exploit code or confirmed active exploitation was identified at time of analysis, and the affected version range is not disclosed in the supplied data - it must be confirmed against IBM advisory node 7292244 before exposure decisions are made.
IBM App Connect Enterprise 13.0.1.0 through 13.0.8.2 can expose sensitive information because components of the product may bind to an unrestricted IP address (for example 0.0.0.0 or a public interface) rather than a loopback or otherwise restricted address, leaving the listener reachable from untrusted networks. IBM's published score is 9.8 CRITICAL (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), but the assessed vector is information disclosure only (C:H/I:N/A:N): a remote, unauthenticated attacker with network reachability to the exposed listener could read data they should not have access to, without user interaction or special conditions. The practical risk is entirely governed by network exposure - deployments that firewall ACE, segment it, or bind listeners to restricted interfaces are largely shielded; no public exploit code and no CISA KEV entry were identified at time of analysis.
Hard-coded cryptographic key in IBM Guardium Data Protection 12.1 and 12.2 means the same static key ships inside every installation, so an attacker who reverse-engineers the product and recovers that key can decrypt (and potentially forge) the data it protects across any deployment. The assessed vector (AV:N/AC:H/PR:N/UI:N) rates this High complexity rather than trivially exploitable, because the attacker must both extract the key and gain access to the ciphertext it guards, and the independent assessment scopes the realistic impact to confidentiality loss rather than integrity or availability. No public exploit code and no CISA KEV listing were identified at time of analysis, and no EPSS score was supplied; the issue is serious but not a top-tier emergency.
Unauthenticated remote write access in IBM DataStage on Cloud Pak for Data 5.4.0.0 lets an attacker manipulate the shared Redis backing store under any tenant's key, collapsing the platform's credential-encryption boundary and allowing cached flow parameters to be poisoned across tenants. The issue is rated CVSS 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N) and requires the multi-tenant deployment pattern where tenants share the same Redis instance. No public exploit was identified at time of analysis, and no CISA KEV entry was provided.
Stack-based buffer overflow (CWE-121) in IBM Planning Analytics 2.0 and 2.1 allows a remote attacker who holds valid low-privilege credentials to overflow an improperly bounds-checked stack buffer and potentially execute arbitrary code on the Planning Analytics server. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 8.8) confirms network reachability, low attack complexity, no user interaction, and high confidentiality, integrity and availability impact, with the credential requirement being the principal limiting factor rather than any technical obstacle. There is no CISA KEV listing and no public exploit code identified at time of analysis, so this is a high-priority patching item rather than an emergency, with exposure driven by how widely authenticated access is granted and whether the service is reachable from untrusted networks.
Hard-coded credentials in IBM Verify Identity Access 11.0.3.1 and IBM Security Verify Access 10.0.9.3 appliances can let an attacker in physical or adjacent-network proximity gain elevated privileges, with CVSS 3.1 score 8.8 reflecting high confidentiality, integrity, and availability impact. The CVSS vector indicates no privileges or user interaction are required (PR:N/UI:N), but the adjacent-network attack vector limits exposure to attackers who can reach the appliance locally or on an adjacent segment. No public exploit code or confirmed active exploitation was identified at time of analysis.
Remote code execution in IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 stems from an improper-authentication weakness (CWE-287) that lets a network-reachable, low-privilege authenticated attacker execute arbitrary code with no user interaction. The CVSS:3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 8.8) indicates full loss of confidentiality, integrity, and availability once the flaw is triggered. No public exploit code was identified at time of analysis, and the vulnerability has not been confirmed as actively exploited (CISA KEV); the primary constraint on attackers is the need for low-privilege authenticated access to the TRIRIGA platform.
Broken object-level authorization in IBM Langflow OSS 1.0.0 through 1.12.4 allows any authenticated low-privilege user to bulk-delete another user's messages, overwrite message content to inject malicious prompts, or reassign a conversation session ID to hijack the session. The CVSS 3.1 score is 8.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L), so exploitation requires a valid account and a shared deployment where other users' messages or sessions exist; single-user instances have little cross-user data to target. No public exploit code or confirmed active exploitation was identified at time of analysis, and this is assessed as above-average priority rather than an emergency.
Local privilege escalation in IBM Sterling Connect:Direct for UNIX (6.3.0.0-6.3.0.7 and 6.4.0.0-6.4.0.6) allows an authenticated local attacker with a low-privileged account to gain elevated privileges through improper privilege management. The CVSS 3.1 score is 8.4 (AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N), reflecting high confidentiality and integrity impact to the host with scope change, but the attack is not remotely reachable. No public exploit was identified at the time of analysis, and exploitation requires an existing local foothold on a host running the affected Connect:Direct components, likely under elevated privileges.
Stored cross-site scripting in IBM Cloud Pak System 2.3.6.0 and 2.3.6.1 allows an authenticated low-privileged user to save JavaScript payloads that execute in another user's browser when the affected page is viewed. The flaw is rated CVSS 7.4 (network-reachable, low privileges, scope change) and requires access to a web-console input field whose value is stored and rendered without proper sanitization or HTML encoding. No public exploit code was identified at time of analysis, and IBM has released a vendor patch.
IBM Concert versions 1.0 through 3.0.0 rely on weaker-than-expected cryptographic algorithms when protecting sensitive data, allowing an attacker who obtains that ciphertext - captured network traffic or exfiltrated at-rest data - to decrypt highly sensitive information. The weakness is confidentiality-only (C:H/I:N/A:N) with no authentication or user interaction required per the CVSS vector, though practical exploitation demands prior possession of the encrypted material and non-trivial cryptanalytic effort, which is why the independently assessed vector rates complexity as High rather than Low. No public exploit code or confirmed active exploitation was identified at time of analysis, and IBM has released a vendor patch.
Heap buffer overflow in IBM MQ Operator and IBM MQ Advanced Container Images lets an authenticated user with authority to perform MQPUT operations crash the queue manager or potentially execute arbitrary code by supplying malformed message options. The advisory is scoped to these containerized IBM MQ products, and exploitation requires valid MQ credentials plus put authority, so this is not an unauthenticated attack. No public exploit identified at time of analysis, and IBM has released a vendor patch.
Denial of service and potential remote code execution in IBM MQ deployments using the MQ Operator and MQ Advanced Container Images result from a heap buffer overflow when an authenticated attacker with put authority sends MQPUT or MQPUT1 operations carrying malformed message handle properties. The CVSS 8.8 vector is network-reachable and requires no user interaction, but the PR:L component means the attacker must already hold valid credentials and put permissions, so the practical threat is an insider or post-compromise actor rather than an unauthenticated remote attacker. No public exploit code was identified at time of analysis, and IBM has released a vendor patch.
Authenticated users of containerized IBM MQ deployments can cause denial of service or memory corruption by sending MQOPEN operations that are not properly validated for buffer size. The affected deployments identified in the CPE data are IBM MQ Operator and IBM MQ Advanced Container Images, with the provided feed using wildcard version fields rather than a precise version range. The vendor CVSS 3.1 score is 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), requiring valid MQ credentials and authority to open a queue or object; no public exploit was identified at time of analysis, and a vendor patch is available via IBM support advisory node 7292667.
Unrestricted Java deserialization in the MQ Classes for Java shipped with IBM MQ Operator (versions 2.0.0 through 4.0.4) and the long list of MQ Advanced container image builds (9.3.0.x, 9.4.x and 10.0.0.x) lets an authenticated low-privilege user trigger a denial of service against the queue manager and, if a usable gadget chain is present on the classpath, potentially execute arbitrary code. The flaw is rated CVSS 8.8 (AV:N/AC:L/PR:L/UI:N, high confidentiality, integrity and availability impact) and requires valid credentials but no user interaction; the specific interface that accepts the serialized stream is not described in the available sources. There is no evidence of active exploitation - the issue is not in CISA KEV, SSVC records exploitation as none and automatable as no, EPSS is only 0.29% (20th percentile), and no public exploit code has been identified at time of analysis; the vuln.today priority is this_week and IBM has published a vendor fix.
Remote code execution in IBM MQ Operator and IBM MQ Advanced container images is possible when a TLS-enabled channel processes a malformed TLS certificate whose distinguished name overflows a stack buffer during connection establishment. 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) because the certificate parsing happens before any authentication completes, so a remote attacker reaching a TLS listener on an affected queue manager needs no credentials and no user interaction; successful exploitation yields full compromise of confidentiality, integrity and availability. Exposure is bounded by configuration: only queue managers whose channels accept or require TLS (for example with SSLCIPH set) reach the vulnerable parsing path. A vendor patch is available, EPSS is low at 0.25% (15th percentile) and SSVC records exploitation as none with automatable no, so no public exploit code has been identified at time of analysis, but the priority label is act_now given total technical impact across a very broad set of shipped container image and operator versions.
Header-driven URI resolution in Apache Camel's HTTP producer components causes message-supplied CamelHttpUri and CamelRestHttpUri values to be expanded through CamelContext.resolvePropertyPlaceholders() before use, so an attacker who can influence those headers turns a URI string into a configuration-evaluation context and can read OS environment variables, JVM system properties, every registered secret-backend PropertiesFunction (AWS, Azure, GCP, HashiCorp, IBM, CyberArk, Kubernetes) and even invoke no-argument methods on beans in the registry. The flaw affects Apache Camel 4.0.0 before 4.18.5 and 4.19.0 before 4.22.1 across camel-http, camel-http-common, camel-vertx-http, camel-undertow and camel-netty-http, and a plain static to(http://backend/api) route is enough to be exposed; no authentication is required where a route is reachable by untrusted senders (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N, 8.2). Exploitation yields a high-confidentiality but limited-integrity impact, and while no public exploit code or CISA KEV entry exists at time of analysis, the preconditions are ordinary and the vendor has shipped fixes, so this warrants prioritised patching.
Local privilege escalation in IBM i 7.3, 7.4, 7.5, and 7.6 allows an authenticated, low-privileged user to obtain QSECOFR/Root authority, as described in CVE-2026-102917. The vulnerability has 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) and requires prior authentication and local access; it is not remotely exploitable. No public exploit code has been identified at time of analysis, and IBM has released a patch via its support advisory.
IBM WebSphere Application Server - Liberty (20.0.0.12 through 26.0.0.10) can be driven into a denial-of-service condition by a remote attacker whose request raises an uncaught exception, degrading availability with no confidentiality or integrity impact. Per the CVSS vector (AV:N/AC:L/PR:N/UI:N), no authentication, privileges or user interaction are required - the only prerequisite is network reachability to an affected Liberty instance, and the exact endpoint or feature that triggers the fault is not described in the available sources. Exploitation has not been confirmed (CISA SSVC: Exploitation none) and no public exploit code has been identified; EPSS is low at 0.32% (23rd percentile), and the CISA SSVC assessment rates automation as possible but technical impact as partial, so prioritization within a weekly patch cycle is appropriate rather than emergency action.
Remote unauthenticated authorization bypass in IBM WebSphere Application Server Liberty 20.0.0.12 through 26.0.0.10 can let attackers reach resources or operations beyond their intended privileges, with high confidentiality and integrity impact and no availability impact. The defect is CWE-863 incorrect authorization, and the supplied sources do not describe the specific trigger, feature, or configuration involved. No public exploit identified at time of analysis; EPSS is 0.33% (24th percentile), while the vuln.today decision label is act_now and CISA SSVC records exploitation none with total technical impact.
Authentication bypass in IBM WebSphere Application Server - Liberty (17.0.0.3 through 26.0.0.10) allows remote, unauthenticated attackers to subvert the SAML 2.0 web single sign-on flow when the samlWeb-2.0 feature is explicitly enabled, resulting in a session fixation condition that yields high confidentiality and integrity impact with no availability impact (CVSS 3.1 base 9.1, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N). Because samlWeb-2.0 is an opt-in Liberty feature rather than a default, only deployments that have configured SAML SSO are in scope; in practice exploitation is most credible when a legitimate user subsequently authenticates through an attacker-influenced session, which is a practical limiting factor relative to the raw vector. There is no public exploit identified at time of analysis, no confirmed active exploitation (no CISA KEV listing), and no EPSS score was supplied with the available intelligence.
Unauthenticated remote attackers can corrupt the persisted status of batch job instances on IBM WebSphere Application Server - Liberty versions 17.0.0.3 through 26.0.0.10 via a deserialization flaw (CWE-502), rated CVSS 3.1 base 8.2 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L). Real-world exposure is limited because exploitation requires the optional, non-default Java Batch / JSR-352 batch management and persistence capability to be enabled on a network-reachable Liberty server, and the resulting impact is confined to the integrity of persisted batch state rather than full server compromise. No public exploit code has been identified and there is no confirmed active exploitation (no CISA KEV listing) at time of analysis.
Access control bypass in IBM WebSphere Application Server - Liberty 20.0.0.12 through 26.0.0.10 allows an unauthenticated remote attacker to call gRPC service methods while evading configured Liberty access controls. This is a genuine high-priority issue by multiple signals, with CVSS 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N), but practical impact is deployment-specific: it matters mainly where gRPC services are deployed and method-level access controls are relied upon. No public exploit identified at time of analysis and no CISA KEV confirmation was provided.
Insufficient isolation in WebSphere Liberty 17.0.0.3 through 26.0.0.10 allows an authenticated attacker who already has low-level privileges on one server instance to cross into other server instances that share the same installation, yielding high confidentiality and integrity impact with a changed scope (CVSS 8.2). Exploitation is conditional: it requires a shared or consolidated install topology and a pre-existing foothold on a co-located server, and the assessment rates this as a genuine but conditional priority rather than a mass-exploitation threat. No public exploit identified at time of analysis.
Denial of service in IBM WebSphere Application Server 8.5 and 9.0, and in IBM WebSphere Application Server - Liberty 17.0.0.3 through 26.0.0.10, allows remote unauthenticated attackers to disrupt availability by sending crafted serialized data to the product's messaging service. The root cause is insecure deserialization (CWE-502) in the messaging component, rated CVSS 3.1 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), so impact is confined to availability - confidentiality and integrity are not affected. Per the assessed vector, no credentials or user interaction are required once the messaging endpoint is reachable, but the vulnerable code path is only exercised where the messaging engine (SIB/JMS) is enabled and accepting input; environments that disable it or restrict it to trusted networks are materially less exposed. There is no public exploit identified at time of analysis, and this CVE is not listed as confirmed actively exploited (CISA KEV).
Cryptographic signature verification bypass in IBM WebSphere Application Server 8.5 and 9.0 and WebSphere Liberty 17.0.0.3 through 26.0.0.10 lets a remote, unauthenticated attacker forge or tamper with signed content that the server should reject, undermining trust in signed tokens and messages (CVSS 8.7, scope-changed integrity and confidentiality impact). Exploitation requires High attack complexity - the attacker must satisfy conditions outside their control when crafting input to reach the flawed verification path - so only deployments that process and validate signed input are realistically exposed. No public exploit identified at time of analysis, and the flaw is not listed in CISA KEV.
Improper authentication in IBM MCP Context Forge prior to 1.0.2 allows remote, unauthenticated attackers to forge HS256-signed JWTs using a JWT_SECRET_KEY shipped in mcpgateway/config.py and .env.example, gaining full platform-administrator access without a database account. The attack requires two conditions to hold simultaneously: the gateway must still use the known shipped signing key, and the platform-admin bootstrap must be active (REQUIRE_USER_IN_DB=false with the token subject set to PLATFORM_ADMIN_EMAIL); because the documented production default for REQUIRE_USER_IN_DB is true, strictly default production deployments are protected, as are operators who rotated the secret before upgrading. Where both conditions are met, forged administrator tokens survive password rotation, account deletion, and session revocation, enabling administrative disclosure, modification, and service disruption; no public exploit code has been identified at time of analysis and the issue is fixed in 1.0.2.
Improper authentication in the CSIv2 inbound propagation handler of IBM WebSphere Application Server 8.5 and 9.0 lets remote, unauthenticated attackers bypass authentication and have forged identity data accepted into the server-side security context, with high confidentiality and integrity impact (CVSS 3.1 base 8.1, AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H). Exploitation is not trivial - it requires network reachability to the CSIv2/IIOP inbound path and a deployment that actually relies on CSIv2 inbound identity propagation, which is what the AC:H metric reflects - and no public exploit identified at time of analysis. IBM has published a vendor fix, so this is best treated as a genuine high-priority issue rather than a drop-everything emergency, with prioritization going to internet- or partner-exposed CSIv2 listeners.
Authorization bypass in IBM WebSphere Application Server 8.5 and 9.0 lets an authenticated, low-privileged user who can reach the cell's management/communication network impersonate an administrator across the entire cell. Because exploitation requires both valid credentials (CVSS PR:L, authenticated) and adjacent-network positioning (CVSS AV:A) rather than open-internet reach, this is a credible mid-to-high priority issue rather than an emergency, although a successful attack yields high confidentiality, integrity, and availability impact. No public exploit code has been identified at time of analysis, and a vendor patch is available per IBM's advisory.
Unauthenticated remote denial of service affecting IBM WebSphere Application Server Liberty (17.0.0.3 through 26.0.0.10) and traditional IBM WebSphere Application Server 8.5 and 9.0, where uncontrolled resource consumption lets a network-reachable attacker degrade or exhaust server availability. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, base 7.5) confirms no authentication or user interaction is required and that impact is confined to availability, with no confidentiality or integrity loss. At the time of analysis no public exploit code has been identified for this issue, and CISA KEV does not list it as confirmed actively exploited; IBM has published a vendor fix via its support advisory at https://www.ibm.com/support/pages/node/7292214.
Out-of-bounds reads in the IBM i File Server allow a remote authenticated attacker to crash or disrupt the service while also leaking portions of adjacent memory, affecting IBM i releases 7.3, 7.4, 7.5 and 7.6. Exploitation is not unauthenticated: the CVSS vector (AV:N/AC:L/PR:L/UI:N) confirms that valid low-privilege credentials and network reachability to the File Server are both required, with high confidentiality and availability impact but no integrity impact, and no user interaction. No public exploit code has been identified at time of analysis, EPSS is low at 0.41% (33rd percentile), CISA SSVC rates exploitation as none and the issue as not automatable, and a vendor patch is available, so this is a moderate-priority patching item rather than an emergency.
Remote code execution and sensitive-information disclosure in IBM i 7.3, 7.4, 7.5, and 7.6 stem from improper data sanitization by the HTTP Server Administration web application (CWE-94 code injection). An authenticated attacker with only low privileges who can reach that administration interface over the network can inject and execute arbitrary code or read sensitive data, with the scope change (S:C) driving Confidentiality, Integrity, and Availability impacts all High for a CVSS 3.1 base score of 9.9. Exploitation is not unauthenticated and is not possible against systems that do not run the HTTP Server Administration interface, or that expose it only to a trusted management network; no public exploit has been identified at time of analysis and there is no CISA KEV confirmation of active exploitation, though IBM has published a vendor patch.
Remote unauthenticated attackers can cause a denial of service in IBM Aspera Enterprise WebApps versions 1.0.0 through 1.0.6 by exhausting resources through uncontrolled resource consumption (CWE-400). The flaw is network-reachable with low complexity, requires no privileges or user interaction, and results in high availability impact, yielding a CVSS 3.1 base score of 7.5. No public exploit code has been identified at time of analysis, and IBM has released a patch.
Local privilege escalation in IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 stems from a misconfigured PATH environment variable (CWE-426) that lets a local attacker place a malicious executable in a directory searched before trusted system paths. Exploitation requires an existing low-privileged foothold on the host and a writable directory on the PATH, yielding high confidentiality, integrity and availability impact (CVSS 7.8, AV:L/PR:L/UI:N). No public exploit code and no confirmed active exploitation were identified at time of analysis; the vendor has published a fix.
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 contains an XML external entity (XXE) injection flaw that allows an authenticated attacker holding an elevated/privileged account to read sensitive information from the application server and, through the changed-scope condition in the CVSS vector, potentially from resources beyond the vulnerable component's own security boundary. Network access with low attack complexity and no user interaction is required, but the PR:H privilege requirement confines realistic exploitation to insiders or attackers who have already obtained privileged credentials, making this a moderate-priority issue rather than an emergency; no public exploit has been identified at time of analysis and the CVE is not listed in CISA KEV.
Session token disclosure in IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 allows a remote authenticated attacker to read session tokens that are rendered directly into HTML response bodies, which can enable session hijacking of whichever account owns the exposed token. The assessed vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, so exploitation requires a valid low-privileged account and the confirmed impact is loss of confidentiality, not direct integrity or availability damage; the practical severity depends on whether tokens belonging to higher-privileged users are exposed rather than only the attacker's own session, in which case impact is minimal. No public exploit code or confirmed active exploitation has been identified at time of analysis, and a vendor patch is available per the IBM advisory.
Authenticated remote code execution in IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 arises from improper validation of file paths inside archives the platform extracts, allowing an attacker with a valid account to write files to arbitrary locations and execute code under the privileges of the TRIRIGA service (CVSS 3.1: 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The attack is network-reachable with no user interaction and low complexity, but the PR:L vector gates it behind an existing authenticated session, confining realistic exploitation to insiders or attackers who have already obtained platform credentials. No public exploit identified at time of analysis, and IBM has published a vendor patch advisory covering the affected 5.0.0-5.0.8 range.
Authenticated low-privileged users on IBM Planning Analytics 2.0 and 2.1 can delete folders and applications belonging to other users because the platform enforces access control at the wrong functional level. The flaw carries a CVSS v3.1 score of 7.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H), with the risk driven almost entirely by the high availability impact of destroyed workspaces rather than by any data disclosure. No public exploit code has been identified at time of analysis, and exploitation requires a valid account on a network-reachable instance, making this most realistically an insider or compromised-credential threat.
Improper authentication in IBM Planning Analytics 2.0 and 2.1 allows an attacker who already holds valid low-privilege credentials to escalate to unauthorized administrative access over the network, with high impact to confidentiality, integrity, and availability (CVSS 3.1 base 8.8, CWE-288). Because the vector carries PR:L, the flaw is not reachable by a fully unauthenticated outsider: the attacker must first obtain ordinary authenticated access to the deployment, after which the alternate-path authentication weakness grants administrative control. No public exploit code has been identified at time of analysis and the issue is not listed as confirmed actively exploited (CISA KEV), but IBM has published a vendor patch, so the primary risk is unpatched, internet- or partner-reachable Planning Analytics installations where low-privilege accounts are widely distributed.
Authentication bypass and privilege escalation in IBM Planning Analytics 2.0 and 2.1 allow an unauthenticated remote attacker to reach functionality that should require credentials by abusing improperly validated sub-requests (CWE-288). Per the assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, exploitation needs only network reachability to the Planning Analytics application interface - no authentication, no user interaction, and no documented non-default configuration - yielding high confidentiality, integrity, and availability impact, which is why the score is 9.8. Signals conflict and must be weighed carefully: despite the severity and total technical impact under SSVC, EPSS is only 0.36% (28th percentile), CISA SSVC records Exploitation: none, and no public exploit code has been identified at time of analysis, so this should be treated as a serious but not yet observed threat. The vendor has released a fix, so exposure is concentrated in unpatched, internet- or partner-reachable deployments.
Arbitrary file write via path traversal in IBM Planning Analytics 2.0 and 2.1 allows remote unauthenticated attackers to write files to arbitrary locations on the server by submitting a crafted URL containing '/../' sequences. The vulnerability carries a CVSS 3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N), indicating high integrity impact but no confidentiality or availability impact. A vendor patch is available per IBM support node 7291604, and no public exploit identified at time of analysis.
Path traversal in IBM Planning Analytics 2.0 and 2.1 allows a remote attacker to read arbitrary files from the host and overwrite certain application files by supplying crafted file paths to the service. The CVSS 3.1 vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N, base 8.2) confirms network reachability, low attack complexity, no authentication requirement (PR:N), and no user interaction, with high confidentiality impact and limited integrity impact. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis; the vendor has released a fix referenced in the IBM advisory.
Authenticated remote code execution in IBM Planning Analytics 2.0 and 2.1 stems from a stack-based buffer overflow (CWE-121) that allows a remote attacker holding valid low-privilege credentials to corrupt stack memory and execute arbitrary code. IBM assigns a CVSS 3.1 base score of 8.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N), and the independent assessment raises the availability impact to High, indicating a successful exploit may also crash or destabilize the affected service. No public exploit code has been identified at time of analysis and the vulnerability is not listed in CISA KEV; vendor patches are available via IBM support node 7291604.
Denial of service in IBM DataStage on Cloud Pak for Data 5.4.0.0 can be triggered by a remote user who already holds valid platform credentials and supplies path traversal sequences to the product's file-handling logic, disrupting or halting the service. Exploitation requires an authenticated session with low privileges (CVSS vector PR:L) and no action by a victim, so the practical barrier is credential access rather than network reachability; availability is the realistic impact, with no evidence of code execution. A vendor patch is available via IBM support advisory node 7288649, and no public exploit code or confirmed active exploitation was identified at time of analysis.
Authenticated path traversal in IBM DataStage on Cloud Pak for Data 5.4.0.0 allows a remote attacker holding a valid platform account to bypass intended directory restrictions and execute arbitrary code. Exploitation requires only low-privileged credentials (CVSS PR:L), needs no user interaction, and is network-reachable with low complexity, which is why the vector scores 9.9 Critical with a scope change (S:C) reflecting impact that can extend beyond the vulnerable component. Despite the high score, the practical risk picture is more moderate: EPSS is only 0.49% (40th percentile), CISA SSVC rates exploitation as none with automatable set to no, there is no public exploit code identified at time of analysis and no KEV listing, and the vendor has published a patch, so remediation is available rather than dependent on compensating controls alone.
Remote OS command execution in IBM DataStage on Cloud Pak for Data 5.4.0.0 allows an authenticated attacker holding only low-privileged credentials to run arbitrary operating system commands on the underlying DataStage host, with high impact to confidentiality, integrity, and availability (CVSS 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The flaw is an OS command injection (CWE-78) in which specially crafted input is passed to a system command without proper neutralization, so no user interaction is required and a single crafted request over the network is sufficient once valid access is obtained. Exploitation is gated by the need for existing credentials on the instance, and there is no public exploit code identified at time of analysis; IBM has published a fix via support node 7288649.
Authenticated remote code execution in IBM DataStage on Cloud Pak for Data 5.4.0.0 allows an attacker who already holds valid low-privilege credentials (CVSS PR:L, AV:N, UI:N) to run arbitrary operating system commands on the underlying host, resulting in high confidentiality, integrity, and availability impact (CVSS 8.8). The root cause is improper neutralization of special elements used in an OS command (CWE-94), meaning user-supplied input reaches a shell command without adequate sanitization. No public exploit code has been identified at time of analysis and the flaw is not confirmed actively exploited (not in CISA KEV), but a vendor patch is available per IBM's advisory, so unpatched 5.4.0.0 deployments exposed to multi-tenant users or broadly provisioned accounts should be prioritized for upgrade.
Man-in-the-middle interception of IBM DataStage on Cloud Pak for Data 5.4.0.0 client sessions lets an attacker who presents a forged TLS certificate capture the IAM bearer Authorization header that the session adapter attaches automatically, granting full platform-scope tenant API access to read and manipulate the victim's DataStage projects, flows, assets, and pipeline definitions. The root cause is CWE-295 improper certificate validation in client-side SDK code running on the user's own machine, so exploitation requires an external network interceptor on the path between that machine and the Cloud Pak for Data platform - a co-tenant inside the shared cluster cannot exploit it - together with an active authenticated session that transmits a live token. CVSS 3.1 scores this 7.4 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N); no public exploit identified at time of analysis, and patch data indicates a fix is available from the vendor.
Unauthenticated network requests to IBM Maximo AI Service 9.1.0 and 9.2.0 can exhaust server resources and render the service unavailable, as described by CWE-400 uncontrolled resource consumption. Per the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, base 7.5), the flaw is network-reachable, low-complexity, and requires no credentials or user interaction, but its impact is confined to availability - there is no data disclosure, data modification, or code execution. IBM has published a vendor patch advisory (https://www.ibm.com/support/pages/node/7290473); no public exploit code and no confirmed active exploitation were identified at time of analysis, so the realistic risk is service downtime for internet- or network-exposed deployments rather than a breach.
Denial of service in IBM Maximo AI Service 9.1.0 and 9.2.0 SaaS allows remote unauthenticated attackers to trigger uncontrolled recursion in an exposed processing path, causing availability impact. The assessed vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, so no privileges or user interaction are required and only availability is affected; no public exploit identified at time of analysis. IBM has released a vendor patch via its support advisory for the identified service levels, and because the product is SaaS, IBM controls the deployed instance and its patching.
Remote code execution in IBM Maximo AI Service 9.1.0 and 9.2.0 lets an unauthenticated remote attacker execute arbitrary code on an affected deployment by abusing improper control of code generation (CWE-94). With 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), the flaw requires no authentication, no user interaction, and no special conditions beyond network reachability of the vulnerable instance. No public exploit code has been identified at time of analysis, and there is no KEV listing; IBM has published an advisory with a vendor fix, so the practical priority is identifying and patching internet- or network-exposed Maximo AI Service 9.1.0/9.2.0 instances.
Denial of service in IBM Maximo AI Service 9.1.0 and 9.2.0 allows unauthenticated remote attackers to terminate the host process by sending malformed frames that the service does not handle correctly. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, score 7.5) confirms that no credentials or user interaction are required, so the only practical gating factor is network reachability to the service endpoint; impact is confined to availability with no data disclosure or modification. No public exploit code has been identified at time of analysis, and the vendor has published a patch advisory.
Denial of service in the IBM Maximo Application Suite IoT Component (versions 9.0.0, 9.1.0, and 9.2.0) allows a remote, unauthenticated attacker to exhaust or crash the service by triggering uncontrolled recursion in its input parsing/processing logic. The flaw carries a CVSS 3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), meaning no credentials or user interaction are required against a network-reachable instance, but the impact is strictly availability - there is no confidentiality or integrity effect. At the time of analysis there is no public exploit identified, and the vendor has released a fix via its support portal.
Memory corruption in IBM Power Systems host firmware FW1060.00 through FW1060.81 lets an attacker who already holds authenticated, high-privileged service-level access to the Flexible Service Processor (FSP) write crafted configuration data that corrupts the host firmware boot stack during system IPL, with the compromise then propagating to the hypervisor loaded by that firmware and to the managed system. Because the flaw is reachable only from the local FSP interface (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H, base 8.2) and only fires on a (re)boot cycle rather than at runtime, the practical attack path is an insider or compromised FSP service account on the management plane rather than a remote network attacker, and no public exploit identified at time of analysis and no CISA KEV listing is associated with this CVE. Full confidentiality, integrity, and availability impact is scored against the managed system, with a scope change reflecting that the corruption begins in host firmware but affects the separately-managed hypervisor.
Authenticated attackers holding service-level credentials on the Flexible Service Processor (FSP) can read or modify arbitrary regions of Hostboot memory on IBM Power Systems firmware levels FW1060.00 through FW1060.81 by sending a specially crafted message over the service processor mailbox interface, corrupting the host firmware boot stack and the hypervisor it subsequently loads. The flaw is rated CVSS 8.2 (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H), with the scope-change rating reflecting that the FSP compromise crosses a boundary into host firmware and produces high confidentiality, integrity, and availability impact on the managed system. Exploitation is gated behind high-privilege service-processor access rather than network reach to the managed OS, and no public exploit code has been identified at time of analysis; no EPSS score was supplied, so it could not be factored into the risk picture.
Local code execution in IBM Power Systems firmware (FW1060.00 through FW1060.81) lets an attacker who already holds authenticated service-level access to the Flexible Service Processor (FSP) send a crafted service processor mailbox message that overflows host firmware runtime attribute storage, compromising the managed system's memory and hardware interfaces. The CVSS 3.1 vector AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H (base 8.2) is internally consistent with that description: the flaw is local, requires high-privilege service-plane credentials, needs no user interaction, and its scope change reflects a jump across the trust boundary from the service processor into the host firmware runtime with high confidentiality, integrity and availability impact. No public exploit code has been identified at time of analysis and there is no CISA KEV entry; IBM published the vendor advisory at https://www.ibm.com/support/pages/node/7290126.
Arbitrary code execution on the host system is possible in IBM Power Systems firmware versions FW1120.00 through FW1120.01, FW1110.00 through FW1110.31, and FW1060.00 through FW1060.81, due to a stack-based buffer overflow (CWE-121) in the host firmware boot process image validation path. An attacker with high-privileged service access to the service processor (PR:H, AV:L) can supply a maliciously crafted code update image to execute arbitrary code on the host system, resulting in full confidentiality, integrity, and availability impact (CVSS 3.1 base score 8.2, High). No public exploit has been identified at time of analysis, and exploitation requires local/service-level access and high privileges, substantially limiting real-world risk.
Arbitrary code execution in the host firmware runtime of IBM Power Systems is possible via the service processor mailbox interface, affecting firmware levels FW1060.00 through FW1060.81. An attacker with authenticated service-level access to the Flexible Service Processor (FSP) can send a crafted mailbox message that overflows host firmware runtime attribute storage (CWE-121), gaining full access to the managed system's memory and hardware interfaces. This is a high-severity local/management-plane issue (CVSS 8.2) requiring high privileges; no public exploit has been identified at time of analysis, and while it is not a mass-exploitation priority, isolation of the FSP network and limiting service accounts are recommended.
Authenticated local access to the IBM Power Systems service processor enables writing crafted host firmware configuration data that crashes the boot stack during system initialization, potentially corrupting memory in firmware versions FW1060.00 through FW1060.81. This stack-based buffer overflow (CWE-121) has a CVSS 3.1 score of 7.3, with limited integrity impact and high availability impact. Exploitation requires service-level credentials (PR:L) and local access to the management plane (AV:L); no public exploit code or active exploitation is identified at time of analysis.
Denial of service in IBM Maximo AI Service 9.1.0 and 9.2.0 lets remote, unauthenticated attackers disrupt the service through improper input validation (CWE-20), with impact limited to availability and no confidentiality or integrity loss. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, base 7.5) indicates the flaw is network reachable, low complexity, and requires no privileges or user interaction, so any deployment exposing the AI Service interface beyond trusted internal networks is at risk. No public exploit code has been identified at time of analysis and the CVE is not listed as confirmed actively exploited (CISA KEV); the practical risk is driven by exposure scope rather than observed attack activity.
Unauthenticated remote attackers can force the IoT Component of IBM Maximo Application Suite 9.0.0, 9.1.0, and 9.2.0 into an infinite parsing loop by submitting crafted input, hanging the parser and degrading or denying availability of the affected service. The flaw is rated CVSS 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), so per the vector no credentials or user interaction are required, but the impact is confined to availability with no data exposure or code execution; the practical exposure depends on whether the IoT parsing interface is reachable from the attacker's network position. There is no indication of confirmed active exploitation (CISA KEV) and no public exploit code identified at time of analysis, and our independent assessment rates this a moderate-priority availability issue rather than a top-tier emergency.
Code injection in the IBM Maximo Application Suite Location Service for Esri component (versions 9.0, 9.1 and 9.2) allows an attacker who already holds high-privilege control over the Kubernetes operator's configuration input - specifically the container image reference consumed from an operator template - to inject a code path that the operator then acts on, resulting in a scope-changing compromise of workloads beyond the operator's own authority (CVSS 3.1 8.7, AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N, CWE-94). The injected image reference can cause attacker-influenced containers to be deployed under the operator's service account, which is why the impact is rated high for confidentiality and integrity even though the attack is not reachable by an unauthenticated outsider against a default deployment. Exploitation is gated by PR:H - the adversary must be able to modify the Location Service for Esri operator's template or custom resource values - no user interaction is required, and there is no public exploit identified at time of analysis.
Command injection in the IBM Maximo Application Suite 'Location Service for Esri' component (versions 9.0, 9.1 and 9.2) allows a highly privileged attacker to execute arbitrary shell commands through a Kubernetes operator task, compromising confidentiality, integrity and availability beyond the component's own security boundary (CVSS 8.7). Exploitation is access-gated rather than trivial: the optional Esri location component must be deployed and enabled, and the attacker must already hold high privileges in the MAS environment (PR:H), but once those two conditions hold there is no user-interaction requirement and attack complexity is low, so injection is straightforward. No public exploit code and no confirmed active exploitation were identified at time of analysis.
Unintended outbound network egress in IBM Maximo Application Suite's optional Location Service for Esri Component (versions 9.0, 9.1, and 9.2) stems from a misconfigured Kubernetes NetworkPolicy that fails to restrict pod egress, allowing traffic to reach destinations the deployment intended to block. Rated CVSS 3.1 base 7.7, the score is driven mostly by the Scope change (S:C) and High confidentiality impact (C:H) rather than ease of attack; the vector (AV:N/AC:L/PR:L/UI:N) indicates remote exploitation at low complexity but with the attacker already holding a low-privileged foothold inside the environment, and no user interaction is needed. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV not listed), so this is best treated as a moderate-priority network-segmentation and data-exposure issue affecting clusters that rely on the shipped NetworkPolicy for egress control.
Improper access control in the Location Service for Esri component of IBM Maximo Application Suite 9.0, 9.1, and 9.2 allows an attacker who already holds high privileges on the underlying Kubernetes/OpenShift platform to abuse a schema-less Custom Resource Definition (CRD) and escalate to full read and write control over affected resources, since the CRD enforces no input validation and the component applies insufficient authorization checks. Exploitation requires authenticated high-privilege access (CVSS vector PR:H), no user interaction, and the optional Esri Location Service add-on to be deployed, so the barrier to entry is significant; the assessed vector is AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H for a base score of 7.2. No public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV), making this a moderate-priority, high-barrier issue rather than an urgent widespread threat - though successful abuse yields high confidentiality and integrity impact on the Maximo environment.
Path traversal in IBM Maximo Application Suite 8.10, 8.11, 9.0, 9.1 and 9.2 lets remote, unauthenticated attackers read arbitrary files from the server by sending crafted URL requests containing '../' sequences. The flaw carries a CVSS 3.1 score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), so impact is confined to confidentiality with no data modification or denial of service, and the independent assessment rates the overall signal as moderate and internally consistent rather than alarming. No public exploit code was identified at time of analysis and the CVE is not listed in CISA KEV; practical exposure depends mainly on internet reachability and on the OS-level file permissions of the account running the Maximo web process, since only files that account can read are disclosed.
Authenticated attackers with low privileges can escalate to elevated privileges on IBM i systems running Db2 Mirror for i 7.4, 7.5, or 7.6 by submitting a crafted request that bypasses additional authorization and input-validation checks, potentially allowing malicious code execution. This critical-severity (CVSS 9.9) privilege escalation affects standard deployments and requires a valid low-privilege account; no public exploit code or active exploitation has been identified at time of analysis, but a vendor patch is available.
Authenticated users of IBM Db2 11.5.0 through 11.5.9 and 12.1.0 through 12.1.5 for Linux, UNIX and Windows (including DB2 Connect Server) can obtain sensitive information they are not authorized to see by issuing the CREATE WRAPPER command, which is improperly authorized. The vulnerability is rated CVSS 3.1 7.7 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N), so it requires a remote attacker to already hold valid Db2 credentials and the privilege to invoke CREATE WRAPPER; there is no integrity or availability impact, making this primarily an insider or compromised-credential risk rather than an unauthenticated breach vector. No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited, but fixed code is available from IBM and should be applied, particularly in environments where federation features are enabled.
Privilege escalation in IBM Db2 LUW (versions 11.5.0 through 11.5.9 and 12.1.0 through 12.1.5 on Linux, UNIX and Windows, including Db2 Connect Server) lets a locally authenticated low-privilege user elevate to higher privileges through improper privilege management, with high impact to confidentiality, integrity and availability and a scope change that can affect resources beyond the vulnerable component. Exploitation is constrained: the attacker must already hold a local foothold on the host and valid low-privilege credentials (CVSS vector AV:L/PR:L/UI:N), so this is not reachable by a remote unauthenticated adversary and realistically affects insiders or attackers who have breached another service on the same host. There is no public exploit identified at time of analysis and the issue is not in CISA KEV; a vendor patch is available, making this a credible, actionable priority for exposed Db2 LUW estate rather than an emergency.
Privilege escalation in IBM Db2 11.5.0 through 11.5.9 and 12.1.0 through 12.1.5 allows a local low-privileged attacker to gain elevated privileges on the Db2 host when the db2locssh feature is enabled. The vulnerability is not remotely reachable and requires an existing local account, making it a post-foothold escalation vector rather than a remote entry point. No public exploit code has been identified at the time of analysis, and IBM has released patches; this is a credible operational priority for environments with db2locssh enabled, but not an emergency.