IBM ContextForge MCP Gateway versions 1.0.0 through 1.0.11 contain a server-side request forgery (SSRF) vulnerability. An authenticated attacker could exploit this flaw to send unauthorized requests from the affected system, potentially enabling network enumeration or aiding other attacks. The vulnerability has a medium severity rating with a CVSS score of 5.4. No patch or remediation information is currently provided.
IBM ContextForge MCP Gateway versions 1.0.0 through 1.0.11 contain an improper access control vulnerability in the bulk import functionality. A remote authenticated attacker with team-scoped admin.import permission can overwrite endpoint URLs, request headers, and authentication credentials of public tools, resources, and prompts owned by other tenants by sending a crafted POST request to the /v1/import endpoint with conflict_strategy=update. This can redirect subsequent AI gateway invocations to an attacker-controlled host.
IBM ContextForge MCP Gateway versions 1.0.0 through 1.1.0 have a vulnerability in improper credential handling. The X-Upstream-Authorization request header can override the gateway-managed upstream credentials for OAuth, bearer, and basic authenticated gateways. This flaw allows an authenticated user to make upstream requests with different credentials, bypassing per-user permission checks and audit attribution.
IBM App Connect Operator and App Connect Enterprise Certified Containers Operands contain a vulnerability that allows an attacker with the ability to run HTTP calls within the running container to make administrative calls to a running IntegrationRuntime. This could lead to high impact on integrity and availability without affecting confidentiality. The vulnerability has a medium severity score of 6.0 and requires high privileges to exploit.
A vulnerability in IBM App Connect Operator and IBM App Connect Enterprise Certified Containers Operands may allow the AI Agent to log sensitive information about the deployed environment within error messages. This exposure could lead to unauthorized disclosure of sensitive data.
IBM ContextForge MCP Gateway versions 1.0.0 through 1.0.11 contain a vulnerability where an authenticated user can bypass upstream credential-level authorization policies. This occurs due to an insufficiently specific cache key in the RFC 8693 token exchange cache, allowing reuse of cached upstream bearer tokens across different credentials of the same user. The vulnerability has a medium severity rating with a CVSS score of 5.4.
A use of default credentials vulnerability exists in multiple Johnson Controls iSTAR Ultra product lines, including iSTAR Ultra, iSTAR Ultra SE, iSTAR Ultra G2, iSTAR Ultra G2 SE, and iSTAR Edge G2. This vulnerability allows unauthorized access due to the use of default credentials. The affected versions are those prior to 2.9.2.CU02 for iSTAR Ultra and prior to 6.9.2.CU02 for the other listed products. The vulnerability is assigned CVE-2025-53697 and has a high severity rating with a CVSS score of 8.4.
IBM ContextForge MCP Gateway versions 1.0.0 through 1.0.11 contain a cross-site scripting (XSS) vulnerability. This flaw allows a privileged user to inject arbitrary JavaScript code into the web user interface, which can alter the intended functionality and potentially lead to credential disclosure within a trusted session. The vulnerability has a medium severity rating with a CVSS score of 4.8.
Devolutions PowerShell Universal versions 2026.3.4 and earlier contain an incorrect privilege assignment vulnerability in the app token management component. This flaw allows an authenticated user with token creation or update permissions to escalate their privileges to administrator. Additionally, in multi-node deployments, a revoked app token can be reinstated by crafting app token requests that set arbitrary roles or revocation states.
IBM ContextForge MCP Gateway versions 1.0.8 through 1.0.11 and 1.1.0 contain a denial of service vulnerability due to an incomplete denylist in the jq filter guard module. An authenticated remote attacker can exploit this by supplying a crafted jsonpath_filter value that bypasses safety checks, causing worker process termination or resource exhaustion. The vulnerability is identified as CWE-184 and has a CVSS 3.1 score of 6.5 (medium severity). No patch or remediation information is currently provided.
A vulnerability in Johnson Controls iSTAR Ultra and iSTAR Ultra SE devices prior to version 6.9.2.CU02 allows functionality bypass due to a missing protection mechanism for an alternate hardware interface. This security flaw is identified as CVE-2025-53698 and is classified with a high severity score of 7. The issue affects versions before 6.9.2.CU02 and relates to CWE-1299. No public exploits or patches are currently documented.
A vulnerability exists in multiple Johnson Controls iSTAR Ultra series devices due to a missing protection mechanism for an alternate hardware interface. This flaw allows functionality bypass as described by CAPEC-554. The affected products include iSTAR Ultra, iSTAR Ultra SE, iSTAR Ultra G2, iSTAR Ultra G2 SE, and iSTAR Edge G2 versions prior to 6.9.2.CU02.
CVE-2025-43874 is an OS Command Injection vulnerability affecting multiple Johnson Controls iSTAR Ultra product lines prior to version 6.9.2.CU02. The flaw involves improper neutralization of special elements in OS commands, which could allow an attacker with limited privileges to execute arbitrary OS commands. The vulnerability has a high severity score of 8.7 but no known exploits in the wild have been reported. A fixed version 6.9.2.CU02 or later is indicated, though no explicit patch link is provided.
A malicious file identified by the SHA-256 hash 8287d65844b6b116dbd3ec838c362577aa33257c192eb8c1107bb190b1668d36 was observed by OffSeq Mirage honeypot sensors on 2026-11-14. This file was detected seven times in attacker activity involving the T1105 technique (Ingress Tool Transfer) originating from attacker infrastructure in the Netherlands. The file is associated with a malicious payload such as a dropper, web shell, miner, or post-exploitation tool. Organizations are advised to check this hash against their environments and security tools to detect potential compromise.
A malicious file identified by the SHA-256 hash ad4ec186ede7f4e22525b1f0d7657a96aa5397f5cb9ea2510ba55677437e8b64 was observed by OffSeq Mirage honeypot sensors on 2026-11-14. This file was seen three times in attacker activity involving the T1105 technique (Ingress Tool Transfer) originating from attacker infrastructure in the Netherlands. The file is associated with a malicious payload such as a dropper, web shell, miner, or post-exploitation tool. Organizations are advised to check for this hash in their environments and security tools.
A malicious file identified by the SHA-256 hash 7905c4ad4267729450a64aee8807b347ba1eb09d35d70afa3b0488ecab2de831 was observed by OffSeq Mirage honeypot sensors on 2026-11-14. The file was detected seven times during attacker activity involving the T1105 technique (Ingress Tool Transfer) from infrastructure located in the Netherlands. This hash corresponds to a specific malicious payload, which could be a dropper, web shell, miner, or post-exploitation tool. Organizations are advised to check this hash against their environments and security tools to detect potential compromise.
A malicious file identified by the SHA-256 hash 08bad1503658a73333a903e2aa8dc28a4f7cddc8eaa6779d2f16ac40128ec8b7 was observed three times on November 14, 2026, by OffSeq Mirage honeypot sensors. The file is associated with attacker activity involving the MITRE ATT&CK technique T1105 (Ingress Tool Transfer). The malicious payload could be a dropper, web shell, miner, or post-exploitation tool delivered or staged during the attack. The attacker infrastructure was located in the Netherlands. This indicator can be used to detect and block the malicious file in affected environments.
A malicious file identified by the SHA-256 hash 6b06d98a817f5f25009af8fdef6a077a750259519fbac9b02176dcf497be0a8e was observed by OffSeq Mirage honeypot sensors on 2026-11-14. This file was detected seven times during attacker activity involving the T1105 technique (Ingress Tool Transfer) originating from attacker infrastructure in the Netherlands. The file hash corresponds to a malicious payload that could be a dropper, web shell, miner, or post-exploitation tool. Organizations are advised to check their environments and security tools for this hash to detect potential compromise.
A malicious file identified by the SHA-256 hash e1e275cf672d481750730a3b46b1d1683ae030573533d3feed87f4e63196a9ac was observed by OffSeq Mirage honeypot sensors on 2026-11-14. The file was detected three times during attacker activity involving the T1105 technique (Ingress Tool Transfer) originating from attacker infrastructure in the Netherlands. This hash corresponds to a specific malicious payload such as a dropper, web shell, miner, or post-exploitation tool. Organizations are advised to check their environments and security tools for this hash to identify potential compromise.
NLTK's CCG lexicon parser function fromstring suffers from a quadratic-time CPU denial of service vulnerability when parsing specially crafted wide bracket bodies or long operator chains. This flaw allows an attacker to cause sustained single-threaded CPU exhaustion by providing a few-megabyte lexicon string, leading to significant availability loss. The vulnerability arises from inefficient string slicing operations in pure-Python loops that scale quadratically with input size. No authentication or user interaction is required, and the vulnerability affects versions prior to 3.10.4. A fix is available in version 3.10.4.