Details
Remediation Advice
Recommended fix:
- Extend the persistent-profile mutation classifier to include
POST /reset-profile. - Reuse the same centralized route classification everywhere the release currently relies on
isPersistentBrowserProfileMutation(...), including:
src/gateway/server-methods/browser.tssrc/node-host/invoke-browser.ts
- Add regression coverage with both:
- a deny control for
POST /reset-profileon the lower-privilegebrowser.requestsurface - an allow control for non-mutating browser profile reads
- Review nearby profile-management routes for any other state-changing endpoints that are still omitted from the mutation classifier.
- Treat
GHSA-vmhq-cqm9-6p7qas the prior family and close the remaining residual route in the same policy surface.