Skip to content

Evenfire is an intelligence layer platform for running LLM agents that take real actions, on your infrastructure

TypeScript

fix: retain official Playwright runtime pending upstream security update

Alfredo Lopez27aa7560929a
diff --git a/.github/workflows/ci-public.yml b/.github/workflows/ci-public.yml
index 3b61e2319..af78dc457 100644
--- a/.github/workflows/ci-public.yml
+++ b/.github/workflows/ci-public.yml
@@ -61,9 +61,6 @@ jobs:
dockerfile: mcp-host/Dockerfile.desktop
context: .
host: true
- - name: playwright
- dockerfile: mcp-servers/playwright/Dockerfile
- context: mcp-servers/playwright
- name: reference-hook
dockerfile: hooks/reference-guardrail-hook/Dockerfile
context: hooks/reference-guardrail-hook
@@ -77,6 +74,7 @@ jobs:
- name: Verify the effective Node runtime
run: |
actual=$(timeout 30 docker run --rm --network none --entrypoint node runtime-smoke -p 'process.versions.node')
+ printf 'NODE_RUNTIME=%s\n' "$actual"
test "$actual" = "$(tr -d '[:space:]' < .nvmrc)"
- name: Verify Host native modules and default SDK transport
if: matrix.variant.host == true
@@ -121,9 +119,6 @@ jobs:
}
});
NODE
- - name: Verify the Playwright application loads on the patched runtime
- if: matrix.variant.name == 'playwright'
- run: timeout 30 docker run --rm --network none --entrypoint node runtime-smoke /app/cli.js --version
test:
name: Build / test / typecheck (${{ matrix.service }})
diff --git a/mcp-servers/package-lock.json b/mcp-servers/package-lock.json
index 51499716c..d3e100f86 100644
--- a/mcp-servers/package-lock.json
+++ b/mcp-servers/package-lock.json
@@ -1,12 +1,12 @@
{
"name": "@clerum/mcp-servers",
- "version": "1.0.10",
+ "version": "1.0.11",
"lockfileVersion": 3,
"requires": true,
"packages": {
"": {
"name": "@clerum/mcp-servers",
- "version": "1.0.10",
+ "version": "1.0.11",
"dependencies": {
"js-yaml": "^4.1.1"
},
diff --git a/mcp-servers/package.json b/mcp-servers/package.json
index fd58e9098..a33a19fbd 100644
--- a/mcp-servers/package.json
+++ b/mcp-servers/package.json
@@ -1,6 +1,6 @@
{
"name": "@clerum/mcp-servers",
- "version": "1.0.10",
+ "version": "1.0.11",
"description": "MCP servers for Clerum testing",
"type": "module",
"main": "index.ts",
diff --git a/mcp-servers/playwright/Dockerfile b/mcp-servers/playwright/Dockerfile
index 5ef8d3f7e..e7060e4fc 100644
--- a/mcp-servers/playwright/Dockerfile
+++ b/mcp-servers/playwright/Dockerfile
@@ -1,9 +1,2 @@
-FROM node:24.22.1-slim@sha256:55fb5f5a527ea2c5c4a95f963e48ef90aa38c7b346054fdc8ee9957a2b55d205 AS node-runtime
-
FROM mcr.microsoft.com/playwright/mcp@sha256:a9d607e571d70954acc36de7a45e7f424a94cebdfba973b1f404435108c60f3f
-# The pinned MCP image bundles Node 22.22.0. Keep its browser dependencies
-# and application, but run them with the patched official glibc Node binary.
-COPY --from=node-runtime /usr/local/bin/node /usr/local/bin/node
-ENV NODE_VERSION=24.22.1
-RUN node -e "if (process.versions.node !== '24.22.1') throw new Error('Unexpected Node runtime')"
RUN node /app/node_modules/playwright/cli.js install chromium
diff --git a/mcp-servers/playwright/README.md b/mcp-servers/playwright/README.md
index b8700c5bc..cef10e527 100644
--- a/mcp-servers/playwright/README.md
+++ b/mcp-servers/playwright/README.md
@@ -2,7 +2,7 @@
MCP server for browser automation, packaging the upstream Microsoft Playwright MCP image (`mcr.microsoft.com/playwright/mcp`, digest-pinned). Uses StreamableHTTP transport on port 8931.
-The [`Dockerfile`](./Dockerfile) keeps the pinned upstream application and browser dependencies, replaces its Node 22.22.0 binary with the official digest-pinned Node 24.22.1 glibc binary, and pre-installs Chromium (`playwright install chromium`). CI verifies the effective Node version and CLI loading on amd64 and arm64. There is no `src/` in this directory, so the tool list remains defined by the upstream [Playwright MCP](https://github.com/microsoft/playwright-mcp) application.
+This is upstream-image packaging, not first-party source: the [`Dockerfile`](./Dockerfile) extends the pinned upstream image and pre-installs the Chromium browser (`playwright install chromium`). There is no `src/` in this directory, so the tool list is defined by the upstream image — per the CRD description, it provides browser automation tools for navigation, DOM interaction, code execution, and screenshot capture. See the upstream [Playwright MCP](https://github.com/microsoft/playwright-mcp) project for the current tool set.
## Environment Variables / Secrets
@@ -21,7 +21,7 @@ docker build -t playwright-mcp-server:latest .
- `scripts/minikube/build-images.sh` optionally builds/reuses it as `clerum/playwright-mcp-server:test` (gated by `MINIKUBE_BUILD_PLAYWRIGHT_MCP_IMAGE`; the default minikube overlay does not deploy it).
- `.github/workflows/build-publish.yml` publishes it to `ghcr.io/evenfire-ai/playwright-server` on changes under `mcp-servers/playwright/`.
-The in-tree `mcpserver.yaml` still pins the upstream image with Node 22.22.0. A security rollout must publish the validated repository image and replace that reference with its multiarch digest. Changing the Dockerfile alone does not update that manifest, and a mutable `latest` reference does not bind it to the validated artifact.
+Note: the in-tree `mcpserver.yaml` currently points directly at the upstream digest-pinned image rather than the locally built one.
## Kubernetes Deployment
@@ -44,3 +44,15 @@ See [`mcpserver.yaml`](./mcpserver.yaml) for the full CRD spec. Key fields:
## Status
Available; deployable via the makefile. No test suite in this directory (unlike `airtable/` and `mongodb/`). Referenced by `docs/crds/context.md` and `charts/clerum-crds/examples/context1.yaml` (a `Context` listing `playwright-server`), and by the `deploy-playwright` target in [`../makefile`](../makefile).
+
+## Node security update status (2026-10-22)
+
+The current upstream digest declares Node 22.22.0. The official `latest`
+(`v0.0.83`), `v0.0.82` and `v0.0.81` image configurations declare Node 24.21.0
+on both amd64 and arm64. These are below the applicable fixed versions in the
+[October 2026 Node advisory](https://nodejs.org/en/blog/vulnerability/october-2026-security-releases).
+
+Keep the official application image and verify an upstream security release
+before updating the deployment digest. The platform's standalone Node upgrade
+does not patch this bundled runtime. This repository does not replace the
+upstream Node binary or publish a custom Node variant for this update.