fix(web): patch js-yaml CPU denial of service - #6796
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
Included review availability: Your plan provides up to 8 included reviews per hour; 6 remain after this review. 📝 SummarySummary by CodeRabbit
WalkthroughThe workspace configuration adds a pnpm override that pins ChangesDependency pinning
Priority: ⬆️ High Estimated code review effort: 1 (Trivial) | ~3 minutes Merge Risk: ⚪ Minimal · up to The dependency update is ready to merge; the pinned version is reflected in the lockfile and validation is passing. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Railway Preview Environment
Updated at 2026-09-12T21:33:50.749Z |
Verification evidenceVerified commit
The broader local package test commands encounter unrelated React test-harness import errors. GitHub's isolated web suite passed on this exact commit. |
Problem
The web lockfile contains js-yaml 4.2.0 and 4.3.1. Three high-severity advisories allow crafted YAML merge structures to consume excessive CPU:
Agenta parses YAML in editors, skill uploads, presets, and trace views.
Change
Resolve every web workspace consumer to js-yaml 4.3.2 through the root pnpm override and regenerate the lockfile.
Validation
pnpm auditno longer reports a js-yaml advisory.The broader package-local Vitest commands currently hit unrelated React test-harness import failures (
act is not a function). The GitHub web suite remains the full regression gate for this exact commit.Base:
release/v0.118.1