fix: patch postcss transitive dep to >=8.5.10 (CVE-2026-41305)#572
fix: patch postcss transitive dep to >=8.5.10 (CVE-2026-41305)#572
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Agent-Logs-Url: https://github.com/maorun/code-stats/sessions/9d40a8fc-a1f1-48bf-adfa-d2507cf4ac0a Co-authored-by: maorun <2291503+maorun@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
This PR mitigates CVE-2026-41305 by forcing the vulnerable transitive postcss@8.4.31 dependency (pulled via next) to resolve to a patched version.
Changes:
- Added an npm
overridesentry to requirepostcss >=8.5.10. - Updated
package-lock.jsonto resolvepostcssto8.5.10(and update its transitive requirements accordingly).
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| package.json | Adds npm overrides to force postcss to a patched version. |
| package-lock.json | Updates the lockfile to resolve postcss to 8.5.10 and refresh related metadata/dependencies. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "eslint": "^8.57.0 || ^9.0.0 || ^10.0.0" | ||
| }, | ||
| "overrides": { | ||
| "postcss": ">=8.5.10" |
There was a problem hiding this comment.
Using an open-ended override range (">=8.5.10") can allow future major releases (e.g., 9.x) to be installed, which may be incompatible with Next’s expected PostCSS major version and can introduce unexpected breakages. Consider constraining the override to the intended major line (e.g., "8.5.10" or "^8.5.10" / ">=8.5.10 <9").
| "postcss": ">=8.5.10" | |
| "postcss": "^8.5.10" |
nextpulls inpostcss@8.4.31as a transitive dependency, which is vulnerable to XSS via unescaped</style>sequences in CSS stringification (CVE-2026-41305, CVSS 6.1). The fix is available inpostcss@8.5.10.Changes
package.json: Added npmoverridesto forcepostcssto>=8.5.10package-lock.json: Resolvedpostcssto8.5.10;npm auditnow reports 0 vulnerabilities