Vault values leaked in plaintext via browser_exec
Cluster 112693. Data as of
Nothing open on GitHub. Fix merged in #113261 on 17 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #113261. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #113261. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug allowed vault-filled secrets to pass through browser_exec without redaction, exposing them in output and persisted state. The accompanying fixes apply redaction to browser_exec output to prevent vault values from reaching the model or storage.
Open issues0
Open PRs0
Fixes on record
-
#113261 fix(browser): browser_exec no longer echoes vault-filled passwords back to the model (#112693, salvage #112699)
files:
tests/tools/test_browser_use_cli.py,tools/browser_use_cli.py
1 PR closed without merging
From the close comments: done elsewhere 1
-
#112699 fix(tools): redact vault values from browser exec output · done elsewhere →
#113261
Closed issues · 1
- Closed#112693[Bug]: Vault egress redaction never reaches browser_exec — vault-filled password echoed in plaintext and persisted to state.db
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #113261
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 17 Sep 2026