Security context
What an agent needs to avoid regressing past fixes and find the next vuln in this repo.
browserbase/stagehand
main @ c02bec8
6
Fixes
1
CVEs
HIGH
Peak severity
16.7%
Coverage
Highlights
Information Disclosure: 2 prior fixes. Scrutinize any change in this area.
.github/workflows: most-fixed (1 issue). Treat as high-risk during review.
2 high-severity fixes in this history; regressions here are high-impact.
Recurring patterns
The bug types that recur here, drawn from past fixes, not open vulnerabilities.
Insecure Workflow Execution: Misconfigured CI/CD triggers on pull request events could allow unauthorized fork contributions to execute with access to privileged repository secrets, resulting in potential credential theft. This was addressed by reverting triggers and restricting test execution for external PRs.
Information Disclosure: Sensitive variables and execution secrets were vulnerable to exposure in persistent caches, console logs, replays, and LLM contexts. Mitigations introduced late-binding substitution systems to mask raw values and maintain placeholders in diagnostic outputs.
Missing Network Access Control: Binding the control server to the wildcard 0.0.0.0 interface exposed the v3 control APIs to the external network. Restricting the binding to localhost prevents unauthorized remote interaction with the Stagehand server.