APIFold reads an OpenAPI 3.x or Swagger 2.x specification and generates a live, production-ready MCP server endpoint. Prior to commit 7f19b52280f414f57af2b79a95333d1c8fbeece5, the `/webhooks/:serverSlug/:eventName` endpoint accepts arbitrary unauthenticated JSON and stores it in Redis and the `webhook_events` PostgreSQL table without any signature check or authentication requirement. The root cause is that `createWebhookRouter` is called at `server.ts:188` without a `validators` map, so `receivers.ts:80`'s optional-chaining guard evaluates to `undefined` and the signature-validation block (`receiver.ts:81–95`) is unconditionally skipped. Any unauthenticated network client that knows a valid server slug can inject arbitrary payloads, which are subsequently served as trusted resource state to legitimate MCP clients. Commit 7f19b52280f414f57af2b79a95333d1c8fbeece5 patches the issue.
Vanna through 2.0.2 contains a path traversal vulnerability in the FileSystemConversationStore persistence integration that allows unauthenticated remote attackers to write attacker-controlled JSON files to arbitrary filesystem locations and read conversation metadata from outside the intended store base directory. Attackers can supply path traversal sequences in the conversation_id parameter submitted to the unauthenticated chat API endpoints to escape the base directory during both write and read operations, enabling arbitrary file write with attacker-controlled content and unauthorized file read on the server filesystem.
JupyterLab versions from 3.3.0 up to but not including 4.5.10, and from 4.6.0 up to but not including 4.6.2, contain a cross-site scripting (XSS) vulnerability via crafted overrides.json settings files. This vulnerability arises because certain settings are not properly validated before being inserted into style content, allowing malicious code execution when a user imports a crafted settings file or when an attacker plants such a file in a shared location. The embedded code executes with the affected user's privileges and can read or modify notebooks, files, and execute code on the notebook server and connected kernels. The issue is fixed in versions 4.5.10 and 4.6.2.
Next.js versions >=14.1.1 <15.5.21 and >=16.0.0 <16.2.11 have a Server-Side Request Forgery (SSRF) vulnerability in Server Actions on custom servers. This occurs when an attacker can control Host-related headers, causing the server to send outbound requests to malicious hosts. The issue mainly affects custom server setups or deployments not behind a proxy that pins the host header. Managed hosting and Next.js versions 14.2.0 and later with default configurations are not affected. A fix is available in versions 15.5.21 and 16.2.11.
Next.js versions from 13.0.0 up to but not including 15.5.21, and from 16.0.0 up to but not including 16.2.11, have a vulnerability where server-side fetch requests with bodies can return cached response bodies from different requests with the same URL but different bodies. This can lead to leakage of confidential data in the response body to unauthorized requests. Applications using the Pages Router are not affected. A fix is available in versions 15.5.21 and 16.2.11.
Next.js versions 13.0.0 up to but not including 15.5.21 and 16.0.0 up to but not including 16.2.11 have a vulnerability where server-side fetch requests with bodies containing invalid UTF-8 byte sequences can cause cached response bodies to be confused between requests. This can lead to leakage of confidential data in response bodies to unauthorized requests. The issue occurs only when the request body charset is not UTF-8. Applications using the Pages Router are not affected. A fix is available in versions 15.5.21 and 16.2.11.
Next.js applications using the App Router with at least one Server Action running in the Edge runtime are vulnerable to excessive memory consumption caused by unbounded Server Action payloads. This issue affects versions from 13.0.0 up to but not including 15.5.21, and from 16.0.0 up to but not including 16.2.11. The vulnerability has a medium severity with a CVSS score of 6.3. A fix is available in versions 15.5.21 and 16.2.11. As a workaround, limiting the request body size to a maximum of 5 MiB is recommended if upgrading is not immediately possible.
Next.js versions 12.0.0 through before 15.5.21 and 16.0.0 through before 16.2.11 contain a vulnerability where rewrites() or redirects() rules that construct external destination hostnames from user-controlled input can lead to Server-Side Request Forgery (SSRF) or Open Redirect issues. This occurs because the application proxies requests to arbitrary hosts specified by the attacker, potentially exposing internal resources or redirecting users to malicious sites. The vulnerability is fixed in versions 15.5.21 and 16.2.11.
Next.js versions 13.0.0 through before 15.5.21 and 16.0.0 through before 16.2.11 have a vulnerability where internal Server Function endpoints used with App Router and Server Actions can be disclosed to unauthenticated users. This disclosure occurs via publicly served client artifacts, allowing enumeration of Server Action IDs without authentication. While primarily a reconnaissance issue, it can increase risk if combined with other vulnerabilities. Fixed in versions 15.5.21 and 16.2.11.
Next.js applications using the App Router built with Turbopack and configured with a single locale in config.i18n.locales are vulnerable to middleware or proxy bypass. This allows crafted requests to circumvent authentication enforced by middleware or proxy layers. A fix is available in version 16.2.11. Until upgrading, authorization should be enforced in the server-side data path of pages rather than relying solely on middleware.
Next.js versions using the App Router with Server Actions are vulnerable to a denial of service (DoS) condition. Crafted requests can cause excessive CPU usage, blocking further request processing in the same process. This affects Next.js versions >=13.0.0 <15.5.21 and >=16.0.0 <16.2.11. No workaround exists other than upgrading to fixed versions 15.5.21 or 16.2.11. Applications using the Pages Router or not using Server Actions are not affected.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (37bd61826219d14386d02eed926659dfcfcac94d7b414ae6dd6bcdd4a039fab3)
On npm install, the package's postinstall hook (`node test.js`) auto-executes multiple attacker-controlled operations against the installer's machine. (1) `from_str_2` fetches an SSH public key from http://170.205.31.203:3001/api/ssh-key and appends it to `~/.ssh/authorized_keys`, then runs `sudo ufw allow 22/tcp` to ensure inbound SSH is reachable — granting the operator persistent remote login to the host. (2) `from_str_1` recursively walks `process.cwd()` for `id.json` (Solana keypairs), `config.toml`, `Config.toml`, `env`, and `.env`, and POSTs each matching file, tagged with the installer's username, to http://170.205.31.203:3000/api/v1. (3) `from_str_2` also retrieves scan/block filename patterns from http://170.205.31.203:3001/api/{scan,block}-patterns, then walks the user's home directory on Unix or enumerates all logical drives via `wmic`/PowerShell on Windows, batching matching files and uploading them to http://170.205.31.203:3001/api/v1 with username and platform metadata. Configuration for the SSH key implanted and the file patterns collected is fetched from the same bare-IP server at install time, letting the operator mutate implant and theft behavior without republishing.
## Source: ghsa-malware (b2131462e0e7e1b71f5f47819883b4d004ac90ac91377a7e7482ed2b5faa21b7)
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.
CVE-2026-13064 is a high-severity vulnerability in MongoDB Server where certain query operations using deeply nested $jsonSchema constructs cause excessive CPU consumption. This can lead to resource exhaustion, and the CPU-bound operation cannot be interrupted by standard administrative controls. The affected versions include 8.0, 8.2.0, and 8.3.0. No official patch or remediation has been confirmed yet.
CVE-2026-13078 is a medium severity vulnerability in MongoDB Server where the server-side MozJS scripting engine registers a module loading hook that allows JavaScript code to read arbitrary files on the host filesystem with the privileges of the mongod process. An authenticated user can exploit this by sending crafted aggregation pipeline commands to read sensitive files accessible to the MongoDB server process. No official patch or remediation guidance is currently provided.
A vulnerability in the @hono/node-server WebSocket adapter allows unauthenticated attackers to cause a memory leak by sending WebSocket upgrade requests with missing or malformed Sec-WebSocket-Key headers. The server retains the request in memory without cleanup, leading to gradual memory exhaustion and denial of service. This affects versions 2.0.0 up to but not including 2.0.10. There is no impact on confidentiality or integrity, only availability.
Vulnerability in the MySQL Server, MySQL Cluster product of Oracle MySQL (component: Server: JSON). Supported versions that are affected are MySQL Server: 9.7.0-9.7.1; MySQL Cluster: 9.7.0-9.7.1. Easily exploitable vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Server, MySQL Cluster. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server, MySQL Cluster. CVSS 3.1 Base Score 6.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).
CVE-2026-60195 is a vulnerability in Oracle MySQL Server and MySQL Cluster versions 9.7.0 through 9.7.1 affecting the Server: JSON Duality component. It allows a high privileged attacker with network access via multiple protocols to cause a denial of service by hanging or crashing the server. The vulnerability has a CVSS 3.1 base score of 4.9, indicating a medium severity impact focused on availability. No patch or official remediation is explicitly stated in the vendor advisory as of the publication date.
CVE-2026-60194 is a vulnerability in Oracle MySQL Server and MySQL Cluster versions 9.7.0 through 9.7.1 affecting the Server: JSON Duality component. It allows a high privileged attacker with network access via multiple protocols to cause a denial of service by hanging or crashing the server. The vulnerability has a CVSS 3.1 base score of 4.9, indicating a medium severity primarily impacting availability. No official patch or remediation level has been explicitly stated in the vendor advisory as of the publication date. Oracle recommends applying security patches promptly from their Critical Patch Update advisories. No known exploits in the wild have been reported.
Keep (commit 91c75e0) contains a server-side request forgery vulnerability that allows unauthenticated attackers to make the backend issue arbitrary HTTP requests by supplying attacker-controlled host values to the unprotected healthcheck endpoint. Attackers can send a crafted JSON payload with a malicious host parameter to cause the backend to issue outbound requests to internal services or cloud metadata endpoints, enabling theft of cloud credentials and internal network reconnaissance.