nextjs - 💡(How to fix) Fix postcss bundled by next is vulnerable to XSS (GHSA-qx2v-qp2m-jg93) — please update to >=8.5.10 [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vercel/next.js#93234Fetched 2026-04-26 05:05:30
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Timeline (top)
closed ×1commented ×1issue_type_added ×1labeled ×1

Code Example

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 25.4.0: Thu Mar 19 19:33:25 PDT 2026; root:xnu-12377.101.15~1/RELEASE_ARM64_T6041
  Available memory (MB): 49152
  Available CPU cores: 14
Binaries:
  Node: 24.13.1
  npm: 11.8.0
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 16.2.4 // No Next.js version data was found.
  eslint-config-next: N/A
  react: 19.2.4
  react-dom: 19.2.4
  typescript: 5.8.3
Next.js Config:
  output: N/A
RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

https://github.com/vercel/next.js/blob/854fdb034e2e85c630c79669901755a3d66f7935/package.json#L252

To Reproduce

Create a new Next.js project (latest stable version). Run npm audit --omit=dev. Observe 3 moderate severity findings referencing postcss < 8.5.10.

Current vs. Expected behavior

Expected Behavior next should bundle postcss >= 8.5.10, which contains the fix for GHSA-qx2v-qp2m-jg93.

Actual Behavior next ships with a nested postcss version below 8.5.10, causing npm audit to flag it.

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 25.4.0: Thu Mar 19 19:33:25 PDT 2026; root:xnu-12377.101.15~1/RELEASE_ARM64_T6041
  Available memory (MB): 49152
  Available CPU cores: 14
Binaries:
  Node: 24.13.1
  npm: 11.8.0
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 16.2.4 // No Next.js version data was found.
  eslint-config-next: N/A
  react: 19.2.4
  react-dom: 19.2.4
  typescript: 5.8.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Not sure

Which stage(s) are affected? (Select all that apply)

Other (Deployed)

Additional context

https://github.com/advisories/GHSA-qx2v-qp2m-jg93

extent analysis

TL;DR

Update the postcss version in the Next.js project to 8.5.10 or higher to fix the moderate severity findings.

Guidance

  • Check the package.json file in the Next.js project to see if postcss is listed as a dependency, and if so, update the version to 8.5.10 or higher.
  • Run npm install [email protected] or higher to update the postcss version.
  • After updating, run npm audit --omit=dev again to verify that the moderate severity findings are resolved.
  • Consider checking the Next.js documentation for any official guidance on updating dependencies.

Example

No code snippet is provided as it is not necessary for this issue.

Notes

The issue is specific to the postcss version used in the Next.js project, and updating to 8.5.10 or higher should resolve the moderate severity findings.

Recommendation

Apply workaround: Update the postcss version to 8.5.10 or higher, as this is a known fix for the GHSA-qx2v-qp2m-jg93 advisory.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

nextjs - 💡(How to fix) Fix postcss bundled by next is vulnerable to XSS (GHSA-qx2v-qp2m-jg93) — please update to >=8.5.10 [1 comments, 2 participants]