Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure agent to attacker-controlled page/file
-
DeliveryInject script into run_command output
-
ExploitPayload stored unescaped in log.html
-
ExecutionOperator opens log in browser
-
ImpactScript exfiltrates transcript contents
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Two chained prerequisites must both hold: (1) the attacker must control content that appears in the agent's observable output - e.g. a web page the agent visits or a file surfaced in run_command output - so that a script payload is captured into the transcript; and (2) a human operator must subsequently open the generated log.html in a browser, at which point the unescaped payload executes. Exploitation is limited to open-computer-use at or before commit 610bac8, is bounded to exfiltrating transcript contents viewable in the operator's browser (no server/system code execution), and cannot fire without the operator-interaction step, materially reducing realistic risk below the network-reachable surface the raw vector suggests. |
| Impact | This is a genuinely low-priority issue, and the signals are consistent rather than conflicting. The vendor-supplied CVSS 4.0 vector (AV:N/AC:L/AT:P/PR:N/UI:P) scores only 2.3, and the multiple dampening factors are real: AT:P reflects that the attacker must first get malicious content into the sandbox's observable output, and UI:P reflects that a human operator must subsequently open the generated log.html. Impact is limited to VC:L/VI:L with no availability impact and no scope/subsequent-system effect (SC:N/SI:N/SA:N), consistent with reflected transcript exfiltration in the operator's browser rather than system compromise. No EPSS score was provided, the CVE is NOT on CISA KEV, and no public exploit code is referenced - only a third-party HackMD write-up and the vulnerable source lines on GitHub. Exploitation status: no public exploit identified at time of analysis. The combination of low technical impact, mandatory attacker-controlled-content + operator-interaction preconditions, and a niche affected product means this is a low-CVSS, low-real-risk hardening fix rather than an urgent patch. Note the CVSS vector claims PR:N (unauthenticated); this is accurate for the operator-side trigger but obscures that the attacker must still achieve control over sandbox content as a practical precondition captured by AT:P. |
| Exploit ScenarioDerived | An attacker lures the open-computer-use agent to a web page or file they control so that attacker-chosen text appears in run_command output; that text contains an HTML/JavaScript payload. Because Logger.write_log_file writes transcript text into log.html without HTML escaping, the payload is stored in the log, and when an operator later opens log.html in a browser the script executes and exfiltrates transcript contents. No public exploit code is referenced, though a third-party HackMD write-up documents the flaw, and the CVSS vector's AT:P/UI:P reflect the required attacker-controlled content and operator interaction. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 11, 2026
Stored cross-site scripting in open-computer-use through commit 610bac8 lets an attacker who controls content the agent observes (such as a web page or run_command output) inject script into the generated log.html, which then executes when a human operator opens the log and can exfiltrate transcript contents. Exploitation requires both attacker-controlled sandbox content and operator interaction, so this is a low-priority issue (CVSS 2.3, CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N) rather than a directly exploitable server-side compromise; no public exploit identified at time of analysis.
RemediationAI
No vendor-released patch identified at time of analysis. The primary fix is to HTML-escape all transcript-derived values before writing them into log.html, for example by using html.escape() on every field written by Logger.write_log_file or by switching to a templating engine with auto-escaping enabled; this preserves log readability while removing executable markup. If upgrading is not possible, compensate by treating generated log.html files as untrusted: open them only in a sandboxed browser, disable JavaScript for local files, or view logs in a text editor instead of a browser. Additional controls include serving logs with a Content-Security-Policy that blocks inline scripts and restricting file-system access to log outputs; these reduce the attack path but do not fix the underlying unescaped output. Consult the VulnCheck advisory (https://www.vulncheck.com/advisories/open-computer-use-through-commit-610bac8-stored-xss-via-log-html-session-log) and the referenced source files for details.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability is CWE-79 improper neutralization of input during web page generation in the e2b-dev open-computer-use project. In os_computer_use/logging.py, Logger.write_log_file writes transcript text into log.html without HTML escaping; sandbox_agent.py collects observable sandbox content, so attacker-controlled web pages or files surfaced in run_command output can carry a payload into the transcript. Because the payload is stored in the log file and runs in the operator's browser when the HTML log is opened, this is a stored XSS whose scope is limited to reading/exfiltrating transcript contents visible in that browser session; there is no server or system code execution. The independent assessment rates it CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N, consistent with two chained prerequisites: attacker-controlled sandbox content and subsequent operator opening of the log.
Know when Open Computer Use gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
AC:H and UI:R because the attacker must seed sandbox content and an operator must open the log; S:C as injected script executes in the operator's browser context, with only limited confidentiality/integrity impact.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
open-computer-use through commit 610bac8 contains a stored cross-site scripting vulnerability in Logger.write_log_file in os_computer_use/logging.py, which writes transcript text into log.html without HTML escaping. Attackers controlling sandbox content, such as web pages or files appearing in run_command output, can inject script that runs when operators open the log, exfiltrating transcript contents.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
EUVD-2026-96888
GHSA-jr77-j87x-vf2g
NVD
CVE.org
EPSS
Exploit-DB