A vulnerability in AdonisJS HTTP Server prior to versions 7.8.1 and 8.2.0 allows an attacker to exploit the response.redirect(). back() method. This method improperly trusts the Referer header from incoming requests and redirects users to that URL without validating the host. An attacker who can control the Referer header can redirect users to malicious external sites. This open redirect issue affects all AdonisJS applications using this method in the specified vulnerable versions.
Kiali 2.11.9, for Red Hat OpenShift Service Mesh 3.1, provides observability for the service mesh by offering a visual representation of the mesh topology and metrics, helping users monitor, trace, and manage efficiently.
Security Fix(es):
* CVE-2025-62718 Axios: Server-Side Request Forgery and proxy bypass due to improper hostname normalization (OSSM-13231, OSSM-13234)
* CVE-2026-25679 Incorrect parsing of IPv6 host literals in net/url (OSSM-12921)
* CVE-2026-29074 SVGO: Denial of Service via XML entity expansion (OSSM-12897, OSSM-12898)
* CVE-2026-29063 Immutable.js: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') (OSSM-12977, OSSM-12978)
* CVE-2026-33186 gRPC-Go: Authorization bypass due to improper HTTP/2 path validation (OSSM-13012)
* CVE-2026-4800 lodash: Arbitrary code execution via untrusted input in template imports (OSSM-13119, OSSM-13120)
* CVE-2026-34986 Go JOSE: Denial of Service via crafted JSON Web Encryption (JWE) object (OSSM-13147)
* CVE-2026-40175 Axios: Remote Code Execution via Prototype Pollution escalation (OSSM-13256, OSSM-13257)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
Kiali 1.73.29 for Red Hat OpenShift Service Mesh 2.6 addresses multiple critical security vulnerabilities including memory exhaustion, server-side request forgery, remote code execution, denial of service, prototype pollution, and authorization bypass. These vulnerabilities affect components such as net/url, Axios, crypto/tls, SVGO, Immutable.js, gRPC-Go, and lodash. The update provides fixes to prevent exploitation of these issues in the service mesh observability tool.
The npm package 'request-easy-validator' impersonates the popular 'request' package and contains malicious code that enables remote code execution. When its exported middleware function is invoked, it silently spawns a detached Node.js process that fetches and executes attacker-controlled code from a mutable URL. This allows an attacker to execute arbitrary Node.js code with full module access on any server using this package. Multiple specific versions of the package are affected.
The npm package 'chai-as-type' is a malicious package impersonating popular assertion libraries. When imported, it downloads and executes attacker-controlled JavaScript code from a remote server, enabling arbitrary code execution in the Node.js environment. The package fetches payloads from mutable public JSON paste hosts, allowing the attacker to update the malicious code dynamically without republishing the package. This behavior can lead to credential theft, persistence, and other malicious activities. The malicious code is triggered either by invoking the exported middleware or running a specific npm script. The affected versions are 7.0.5 and 1.1.9.
ApostropheCMS is an open-source Node.js content management system. Versions 4.28.0 and prior contain a stored cross-site scripting vulnerability in SEO-related fields (SEO Title and Meta Description), where user-controlled input is rendered without proper output encoding into HTML contexts including <title> tags, <meta> attributes, and JSON-LD structured data. An attacker can inject a payload such as "></title><script>alert(1)</script> to break out of the intended HTML context and execute arbitrary JavaScript in the browser of any authenticated user who views the affected page. This can be leveraged to perform authenticated API requests, access sensitive data such as usernames, email addresses, and roles via internal APIs, and exfiltrate it to an attacker-controlled server. This issue has been fixed in version 4.29.0.
The BackWPup WordPress plugin up to version 5.6.6 contains a path traversal vulnerability in the /wp-json/backwpup/v1/getblock REST endpoint via the block_name parameter. This flaw allows authenticated users with Administrator-level access or higher to include arbitrary PHP files on the server by exploiting insufficient sanitization of traversal sequences. This can lead to reading sensitive files like wp-config.php or potentially remote code execution depending on server configuration. Permissions granted to lower-level users to handle backups may also enable exploitation by those users. The vulnerability has a high severity score of 7.2 and no official patch or remediation guidance has been provided yet.
SvelteKit is a framework for rapidly developing robust, performant web applications using Svelte. Prior to 2.57.1, redirect, when called from inside the handle server hook with a location parameter containing characters that are invalid in a HTTP header, will cause an unhandled TypeError. This could result in DoS on some platforms, especially if the location passed to redirect contains unsanitized user input. This vulnerability is fixed in 2.57.1.
A vulnerability in Node.js TLS error handling can cause denial of service by crashing or exhausting resources of a TLS server when using pskCallback or ALPNCallback. Uncaught synchronous exceptions during these callbacks bypass standard TLS error handling, leading to process termination or resource leaks. This affects Node.js versions where these callbacks throw exceptions without safe wrapping. Red Hat Hardened Images RPMs have been updated with fixes for this issue. Systems configured per Red Hat guidelines should automatically restart services on crash, mitigating availability impact.
OpenClaw versions before 2026.3.25 have a vulnerability where JSON request bodies are parsed before webhook signatures are validated. This allows unauthenticated remote attackers to send malicious webhook requests that trigger resource-intensive JSON parsing, potentially causing a denial of service by exhausting server resources.
SiYuan is a personal knowledge management system. Prior to 3.6.4, SiYuan configures Mermaid.js with securityLevel: "loose" and htmlLabels: true. In this mode, <img> tags with src attributes survive Mermaid's internal DOMPurify and land in SVG <foreignObject> blocks. The SVG is injected via innerHTML with no secondary sanitization. When a victim opens a note containing a malicious Mermaid diagram, the Electron client fetches the URL. On Windows, a protocol-relative URL (//attacker.com/image.png) resolves as a UNC path (\\attacker.com\image.png). Windows attempts SMB authentication automatically, sending the victim's NTLMv2 hash to the attacker. This vulnerability is fixed in 3.6.4.
## Impact
An authenticated Server-Side Request Forgery in `n8n-mcp` allows a caller holding a valid `AUTH_TOKEN` to cause the server to issue HTTP requests to arbitrary URLs supplied through multi-tenant HTTP headers. Response bodies are reflected back through JSON-RPC, so an attacker can read the contents of any URL the server can reach — including cloud instance metadata endpoints (AWS IMDS, GCP, Azure, Alibaba, Oracle), internal network services, and any other host the server process has network access to.
The primary at-risk deployments are multi-tenant HTTP installations where more than one operator can present a valid `AUTH_TOKEN`, or where a token is shared with less-trusted clients. Single-tenant stdio deployments and HTTP deployments without multi-tenant headers are not affected.
## Affected versions
`n8n-mcp` ≤ `2.47.3` (all versions up to and including 2.47.3).
## Patched versions
`n8n-mcp` `2.47.4` and later.
## Workarounds
If you cannot immediately upgrade:
1. **Egress filtering at the network layer** — block outbound traffic from the `n8n-mcp` container to RFC1918 ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), link-local `169.254.0.0/16`, and any other internal ranges. This defends against any future SSRF-class issue and is recommended even after upgrading.
2. **Disable multi-tenant headers** — if your deployment does not require per-request instance switching, unset `ENABLE_MULTI_TENANT` and do not accept `x-n8n-url` / `x-n8n-key` headers at the reverse proxy.
3. **Restrict `AUTH_TOKEN` distribution** — ensure the bearer token is only held by fully trusted operators until you can upgrade.
## Remediation
Upgrade to `n8n-mcp` 2.47.4 or later. No configuration changes are required; the fix adds validation at the URL entry points and normalizes URLs at the API client layer.
## Credits
Reported by the Eresus Security Research Team. @ibrahmsql
sjs-biginteger typosquats big.js on npm. Published April 7, 2026 by throwaway account vanes.s.p.orit.a, the package ships legitimate big.js source and hides its payload in a dependency: sjs-lint-build1. On install, the dependency’s postinstall hook fetches the attacker’s SSH public key from a C2 server, appends it to ~/.ssh/authorized_keys, opens firewall port 22, then collects SSH keys, environment variables, config files (.env, Solana id.json, config.toml), and system fingerprints. It exfiltrates the collected data to two Vercel-hosted C2 domains disguised as Cloudflare services.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (ad825f5a8f4892374c8e1f8a4d1e5e84e28419eb656035667c4c9d8964966f6d)
The package sjs-biginteger was found to contain malicious code.
## Source: ghsa-malware (fcae78c041d8a88f2709f71788ac5b4e4e5f5f17862874f05e4a3742e9f4f464)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
sjs-biginteger typosquats big.js on npm. Published April 7, 2026 by throwaway account vanes.s.p.orit.a, the package ships legitimate big.js source and hides its payload in a dependency: sjs-lint-build1. On install, the dependency’s postinstall hook fetches the attacker’s SSH public key from a C2 server, appends it to ~/.ssh/authorized_keys, opens firewall port 22, then collects SSH keys, environment variables, config files (.env, Solana id.json, config.toml), and system fingerprints. It exfiltrates the collected data to two Vercel-hosted C2 domains disguised as Cloudflare services.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (cba6ed57b1eb82592650453ea703d44d9294be1c1c3316f4562ff4f197e6c0f6)
The package sjs-lint-build1 was found to contain malicious code.
## Source: ghsa-malware (fc8bd742b46dcad52a23f2cef1c0c23ede56a1f36828c95a07b23ebef5c47715)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Unfurl before 2026.04 contains an unbounded zlib decompression vulnerability in parse_compressed.py that allows remote attackers to cause denial of service. Attackers can submit highly compressed payloads via URL parameters to the /json/visjs endpoint that expand to gigabytes, exhausting server memory and crashing the service.
CVE-2026-39890 is a critical vulnerability in MervinPraison PraisonAI versions prior to 4.5.115. The vulnerability arises from unsafe deserialization of YAML files using the js-yaml library without disabling dangerous tags, allowing attackers to execute arbitrary JavaScript code remotely by uploading malicious agent definition files. This leads to remote code execution on the server hosting the vulnerable application. The issue is fixed in version 4.5.115. No known exploits in the wild have been reported yet.
CVE-2026-39885 is a Server-Side Request Forgery (SSRF) vulnerability in the frontmcp product by agentfront, specifically in versions prior to 1.0.4. The vulnerability arises because the mcp-from-openapi library uses @apidevtools/json-schema-ref-parser to dereference $ref pointers in OpenAPI specifications without restricting URLs or using custom resolvers. This allows malicious OpenAPI specs to cause the server to fetch internal network resources, cloud metadata endpoints, or local files during initialization, enabling SSRF and local file read attacks. The vulnerability has a high severity with a CVSS score of 7.5. No official patch or remediation level is explicitly stated in the provided data, but the description notes the issue is fixed in version 2.3.0 of the framework, which suggests upgrading to a fixed version is the recommended mitigation.
CVE-2026-5803 is a server-side request forgery (SSRF) vulnerability in the bigsk1 openai-realtime-ui product, specifically in an unknown function within the server.js file of the API Proxy Endpoint component. The vulnerability allows remote attackers to manipulate a query argument to induce SSRF. The issue affects versions up to commit 188ccde27fdf3d8fab8da81f3893468f53b2797c. A patch identified by commit 54f8f50f43af97c334a881af7b021e84b5b8310f is suggested to address the issue. The CVSS 4.0 base score is 5.3, indicating medium severity. No official remediation level or detailed vendor advisory is provided, and no known exploits in the wild have been reported.