fix: upgrade postcss to >=8.5.12 to address CVE-2026-45623#3067
Conversation
|
🧪 E2E Test Results❌ Some tests failed Summary
❌ Failed Tests▲ Vercel Production (7 failed)astro (1 failed):
example (2 failed):
fastify (1 failed):
hono (1 failed):
nextjs-turbopack (1 failed):
vite (1 failed):
📦 Local Production (1 failed)nextjs-turbopack-canary (1 failed):
📋 Other (1 failed)e2e-vercel-prod-nest (1 failed):
Details by Category❌ ▲ Vercel Production
✅ 💻 Local Development
❌ 📦 Local Production
✅ 🐘 Local Postgres
✅ 🪟 Windows
❌ 📋 Other
✅ vercel-multi-region
❌ Some E2E test jobs failed:
Check the workflow run for details. |
📊 Workflow Benchmarkscommit Backend:
Best/P75/P90/P99 deltas compare against the most recent benchmark run on Metrics — TTFS: time to first step body (in-deployment start() → first step body, deployment clocks) · STSO: step-to-step overhead (gap between consecutive step bodies) · WO: workflow overhead (whole-run time outside step bodies, in-deployment anchored) · SL: stream latency (in-deployment write → read propagation, readAt - writtenAt) Scenarios — step: one trivial no-op step, no stream; no hooks, so the run stays in turbo mode (in-process fast path) · stream: one streaming step; no hooks, so the run stays in turbo mode (in-process fast path) · hook + stream: registers a hook before one step, which exits turbo mode (dispatch path) · 1020 steps: 1020 trivial sequential steps; STSO is measured between consecutive steps in the given step ranges, and WO is the whole-run overhead outside step bodies · stream latency: parallel reader/writer steps on a dedicated stream; SL is the in-deployment write->read propagation (readAt - writtenAt) 🔴 marks a percentile over its target (within target is left unmarked). Targets (p75/p90/p99, ms) — TTFS 200/300/600 · SL 50/60/125 · STSO (1-20) 20/30/60 · STSO (101-120) 30/45/90 · STSO (1001-1020) 40/60/120 All metrics are measured from deployment-side timestamps only. Runs are triggered by an in-deployment route that stamps the anchor ( Cold starts are kept in the numbers on purpose — they are part of real bursty-workload latency. The workbench deployment cold-starts the |
There was a problem hiding this comment.
Pull request overview
This PR updates postcss in private workspaces to remediate CVE-2026-45623 by ensuring direct workspace dependencies no longer allow resolving vulnerable <8.5.12 versions, and refreshes the lockfile to remove postcss@8.5.6.
Changes:
- Bump
postcssto^8.5.12inworkbench/swc-playgroundanddocs. - Update
pnpm-lock.yamlso direct resolutions move topostcss@8.5.16andpostcss@8.5.6is removed.
Reviewed changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| workbench/swc-playground/package.json | Bumps the workspace devDependency postcss floor to a patched version. |
| docs/package.json | Bumps the workspace devDependency postcss floor to a patched version. |
| pnpm-lock.yaml | Removes postcss@8.5.6 and updates resolved postcss versions to 8.5.16. |
Files not reviewed (1)
- pnpm-lock.yaml: Generated file
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
Backport to This is usually an infrastructure problem (e.g. the configured AI model could not be found, an AI Gateway error, or an opencode crash) rather than a merge conflict. Check the job logs linked above for details. Once the underlying issue is fixed, re-run the Backport to stable workflow manually via |
Fixes VULN-13433
Summary
Socket.dev flagged
postcss@8.5.6(CVE-2026-45623, CVSS 7.5 High) — arbitrary file read / information disclosure via attacker-controlledsourceMappingURLcomments in CSS input. Affected versions are< 8.5.12.Changes
workbench/swc-playground/package.json: bumppostcssfrom^8.5to^8.5.12(the manifest the alert was filed against)docs/package.json: bumppostcssfrom^8.5.6to^8.5.12— this workspace resolved the same vulnerable8.5.6in the lockfilepnpm-lock.yaml:postcss@8.5.6is fully removed; both workspaces (and the transitive@tailwindcss/postcss/ vite consumers) now resolvepostcss@8.5.16Notes
docs,workbench/swc-playground) are affected (pnpm changeset status --since=mainpasses)postcss@8.4.31remains in the lockfile (pinned by Next.js internally); it is not addressable via these manifests and is outside the scope of this alert, which targets the direct dependency