Node.js versions 22.x, 24.x, and 26.x contain a vulnerability in TLS hostname verification where server certificates can be incorrectly validated against a different IP address when the host is specified as a non-canonical IPv4 literal with leading zeros. This occurs because the hostname normalization interprets leading-zero octets as octal, while the OS resolver interprets them as decimal, potentially allowing a server to be authenticated with a certificate for another IP address.
Tandoor Recipes versions before 2.7.0 have a server-side request forgery (SSRF) vulnerability in the Pestle importer. Authenticated low-privileged users can craft malicious image URLs in Pestle JSON import files to make the server issue arbitrary GET requests to internal or external hosts. This bypasses the centralized SSRF filter and allows attackers to access internal endpoints, perform port and service discovery, and exfiltrate internal responses via stored recipe images. The vulnerability is fixed in version 2.7.0.
Uni-CLI versions prior to 0.225.2 exposed a legacy JSON-RPC-over-HTTP transport on localhost without validating browser Origin headers. This allowed malicious web pages to send CORS POST requests to the local /mcp endpoint and execute JSON-RPC commands against the local Uni-CLI server if the MCP HTTP transport was active. The issue was due to inconsistent enforcement of the browser-to-localhost boundary between two HTTP transports. This vulnerability has been fixed in version 0.225.2.
baserCMS versions 5.0.0 before 5.3.2 and 5.4.0 before 5.4.2 contain a deserialization vulnerability in the widget-area entity. This flaw allows an administrator or an attacker with widget-write capability to store malicious serialized objects via the admin JSON API. These objects are deserialized without restrictions, enabling remote code execution as the web-server user upon unauthenticated page requests. The issue has been fixed in versions 5.3.2 and 5.4.2.
The @grabcad/preferences-client npm package is a malicious package that acts as a dependency confusion attack vector. It exports a Proxy that returns no-op functions but executes a beacon script on import and post-install, sending sensitive environment information to an attacker-controlled server. This reconnaissance behavior discloses internal hostnames, install paths, and Node.js version to a hostile endpoint. Systems with this package installed should be considered fully compromised, and all secrets and keys must be rotated immediately from a different machine.
CVE-2026-114643 is a vulnerability in the MongoDB C# Driver where GeoJSON extra members are written without checking for name collisions with reserved GeoJSON members like type and coordinates. This can cause documents to have duplicate geometry fields, leading to inconsistencies between the server and driver in resolving record values. Affected records may become unreadable through the driver, disrupting application code that reads them.
CVE-2026-94482 is a high-severity vulnerability in the Next.js React framework affecting versions from 13.0.0 up to but not including 15.5.28 and from 16.0.0 up to but not including 16.4.1. Crafted requests targeting App Router applications with at least one Server Action can cause excessive CPU consumption, leading to blocking of further request processing in the same process. Applications using the Pages Router or App Router without Server Actions are not affected. The issue is fixed in versions 15.5.28 and 16.4.1.
A vulnerability in Vite versions 8.2.0 up to but not including 8.3.3 allows an attacker to retrieve the first 4 bytes of files outside the configured server.fs directory by sending a request with the ?vite-wasm-instance query. This occurs because the internal Wasm plugin's load hook reads files without applying server.fs restrictions and exposes the first 4 bytes in error messages when WebAssembly parsing fails. The issue affects setups where the Vite dev server is exposed to the network and is run using Node.js or Deno. A fix is available in version 8.3.3.
A path traversal vulnerability (CWE-22) in Storybook development server versions from 8.0.0 up to but not including 8.6.19, 9.0.0 up to 9.1.21, 10.0.0 up to 10.6.2, and 11.0.0-alpha.0 up to 11.0.0-alpha.6 allows an attacker on the local network to obtain the WebSocket authentication token. This token can be used to invoke file-writing or testing functionality, potentially leading to code execution if the Vitest addon is installed with an old Vitest version. The issue is fixed in versions 8.6.19, 9.1.21, 10.6.2, and 11.0.0-alpha.6.
CVE-2026-114125 is a code injection vulnerability in Storybook, a frontend UI component development tool. Versions from 8.0.0 up to but not including 8.6.19, 9.0.0 up to 9.1.21, 10.0.0 up to 10.6.2, and 11.0.0-alpha.0 up to 11.0.0-alpha.6 are affected. The flaw allows a malicious website to interact with the preview iframe of a running Storybook development server due to insufficient iframe embedding and message-origin restrictions. An attacker can cause unauthorized changes to story files if a developer visits and interacts with the malicious site, potentially leading to arbitrary code execution with the developer's privileges when the modified files are executed locally. Fixed versions include 8.6.19, 9.1.21, 10.6.2, and 11.0.0-alpha.6.
SvelteKit versions from 2.10.0 up to but not including 3.0.0 contain a path traversal vulnerability in the vite preview server on Windows. This flaw allows unauthenticated attackers with network or tunnel access to the preview server to read files outside the intended prerendered output directory. Exploitation can expose sensitive files such as source code, configuration files, or credentials accessible by the server process. The vulnerability is fixed in version 3.0.0.
SvelteKit versions before 3.0.0 have a server-side request forgery (SSRF) vulnerability. This flaw allows remote attackers to exploit self-fetch fallbacks that automatically follow HTTP redirects. By manipulating the Host or forwarded headers, attackers can redirect fallback requests to internal services, potentially exposing them.
CVE-2026-101785 is a security vulnerability affecting MySQL Server and MySQL Cluster, specifically related to the JSON server component. It impacts multiple MySQL versions including 8.0, 8.4, and 9.7, as well as specific MySQL 5.5 versions used in Ubuntu distributions. The vulnerability was published on October 26, 2026, and is rated with medium severity. Oracle has included this vulnerability in its October 2026 Critical Patch Update, which contains numerous security patches across various Oracle products including MySQL. Oracle strongly recommends applying available patches promptly to mitigate risks associated with this vulnerability.
CVE-2026-101733 is a security vulnerability affecting MySQL Server and MySQL Cluster, specifically related to the JSON server component. It impacts MySQL versions 8.0, 8.4, and 9.7. The vulnerability has been publicly disclosed and is classified with medium severity. Oracle has included this vulnerability in its October 2026 Critical Patch Update, which contains numerous security patches across multiple products including MySQL. Oracle strongly recommends applying the available patches promptly to mitigate the risk. There are no known exploits in the wild at this time.
CVE-2026-101616 is a medium severity vulnerability affecting MySQL Server and MySQL Cluster, specifically related to the JSON server component. It impacts multiple MySQL versions including 8.0, 8.4, and 9.7, as well as various Ubuntu 14.04-specific MySQL 5.5 builds. Oracle has included this vulnerability in its October 2026 Critical Patch Update, which contains numerous security patches across many products.
A vulnerability in @modelcontextprotocol/server versions 2.0.0 through 2.2.0 allows an MCP server accessed over HTTP to deliver one client's responses and notifications to another client when clients share a stateless transport or a single server instance. This occurs because messages are matched only by JSON-RPC id, which can collide. The issue is fixed in version 2.3.0 and later, but requires code changes to avoid sharing SDK clients or server instances across multiple clients.
CVE-2026-113672 is a critical path traversal vulnerability in Argo CD's repo-server affecting versions from 0.9.0 up to certain fixed releases. The flaw allows crafted .jsonnet files to import files outside the repository root, exposing sensitive files such as service-account tokens and private keys. Attackers with Application get permission can exploit this without needing update, sync, or repository write access. The issue is fixed in versions 3.3.15, 3.4.10, 3.5.4, and 3.6.0-rc2.
## Review scope and evidence limits
Package: @apostrophecms/import-export, version 3.7.0.
Release tag reviewed: @apostrophecms/import-export@3.7.0, commit 9500b8b0e1d630d5e07fbb5fd2c25ed0943845ce (September 30, 2026).
Current main reviewed: 5ce3732be0ebdebb4db0f8ef160c81e8671157e6.
The importer, gzip extractor, import permission gate, and core permission implementation have no differences between that release tag and the reviewed main. This follow-up is a static remediation review. We have not repeated the original end-to-end reproductions against the latest release or tested a deployed site. Current exploitability and impact therefore still require maintainer validation; the observations below establish that the reported security checks remain absent in public source. The original emailed PDF contains the original reproduction material. Please refer to that existing private attachment.
## Archive duplicate continuation permits unauthorized published-content replacement
The overrideDuplicates() continuation still accepts client-supplied replacement choices, rather than binding them to a server-maintained, user-owned duplicate analysis. The replacement and write helpers do not establish a single canonical resource identity and authorization context before the update. This leaves the reported gap between draft editing authority and the published target selected for replacement unresolved at source level.
The original report describes a contributor crossing the publication boundary through duplicate replacement on an import-enabled localized type. We have not repeated that end-to-end sequence on 3.7.0.
Suggested remediation: bind continuation state to the initiating user, archive, job, permitted source/target mapping, locale and mode; reject inconsistent identity metadata; derive permissions from the actual loaded target and require publication authority for published targets.
Source: overrideDuplicates(), replaceDocId(), and insertOrUpdateDoc() in the [importer](https://github.com/apostrophecms/apostrophe/blob/5ce3732be0ebdebb4db0f8ef160c81e8671157e6/packages/import-export/lib/methods/import.js).
## Coordination
Vivek R / Winfunc
Original reporting team: Mufeed VH / Winfunc
### Summary
The color field accepts any string that *begins* with a valid `rgb()` / `hsl()` color, because `TinyColor.isValid` does not anchor its match at the end of the string. An authenticated user with edit rights can store arbitrary HTML after a valid color prefix. When the stored value is rendered , the payload executes, resulting in stored XSS.
### Details
Server-side validation of the color field relies on TinyColor:
```js
const { TinyColor } = require('@ctrl/tinycolor');
if (!new TinyColor(value).isValid) throw self.apos.error('invalid');
```
TinyColor's `rgb`/`hsl` matchers are not anchored at the end of the string, while hex matchers are. Tested with @ctrl/tinycolor
| Input | `isValid` |
|---|---|
| `rgb(1,2,3)<img src=x onerror=alert(1)>` | `true` |
| `rgb(1,2,3)</textarea><script>alert(1)</script>` | `true` |
| `hsl(0,100%,50%);--x:1}</style><script>alert(1)</script>` | `true` |
| `#ff0000<img src=x onerror=alert(1)>` | `false` |
The value is saved to MongoDB unchanged (not normalized to hex8).
### Relation to GHSA-97v6-998m-fp4g
GHSA-97v6 addressed CSS custom property injection escaping a `<style>` context. The root cause (validation that accepts trailing content after a valid color) still exists in <= 4.32.2, so [FILL IN: either "the style-tag sink remains exploitable via `</style>`" OR "a separate HTML sink at X is exploitable"]. Fixing the validation (requiring the full string to be a color, or storing only TinyColor's normalized output) would close both.
### Impact
Any user with edit permission can plant persistent JavaScript that runs in the browser of visitors and administrators viewing the affected page, enabling session hijacking and actions as an admin.
### Suggested fix
Reject values unless the entire string is a valid color, e.g. normalize on save:
```js
const c = new TinyColor(value);
if (!c.isValid) throw self.apos.error('invalid');
value = c.toHex8String(); // store only normalized output
```