<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-07T14:27:34.635874+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-352608</id>
    <title>EUVD-2026-352608</title>
    <updated>2026-10-07T14:27:34.688877+00:00</updated>
    <content>EUVD-2026-352608</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-352608"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-49143</id>
    <title>fkie_cve-2026-49143</title>
    <updated>2026-10-07T14:27:34.688916+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>BrowserStack Runner through 0.9.5 contains a remote code execution vulnerability in the /_log HTTP handler that allows unauthenticated network-adjacent attackers to execute arbitrary code by submitting crafted JSON request bodies to the handler, which passes user-supplied data to vm.runInNewContext() combined with eval(). Attackers can escape the Node.js vm sandbox by leveraging a host-context Function reference through util.format to access the host process via this.constructor.constructor, achieving full remote code execution on the underlying system without any authentication.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-49143"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-6vr3-7wcx-v5g5</id>
    <title>GHSA-6vr3-7wcx-v5g5 — browserstack-runner vulnerable to Remote Code Execution via vm sandbox escape in _log HTTP handler</title>
    <updated>2026-10-07T14:27:34.688958+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: browserstack-runner</p>
<p>### Summary</p>
<p>The HTTP handler `/_log` in `lib/server.js` (lines 491–515) of browserstack-runner passes unauthenticated user-supplied data to `vm.runInNewContext()` combined with `eval()`, enabling a sandbox escape and arbitrary code execution on the host system.</p>
<p>### Details</p>
<p>When `browserstack-runner` starts, it creates an HTTP server on port 8888 (configurable) that listens on all network interfaces (`0.0.0.0`). The `/_log` endpoint accepts POST requests and processes the JSON body as follows:</p>
<p>```javascript
// lib/server.js lines 504-510
var context = { input: query.arguments, format: util.format, output: '' };
var tryEvalOrString = 'function (arg) { try { return eval(\'o = \' + arg); } catch (e) { return arg; } }';
vm.runInNewContext('output = format.apply(null, input.map(' + tryEvalOrString + '));', context);
```</p>
<p>The `vm` module is [not a security mechanism](https://nodejs.org/api/vm.html#vm-executing-javascript) per Node.js documentation. The `context` object contains a reference to `util.format` (a host-context Function), enabling sandbox escape via `this.constructor.constructor("return process")()`.</p>
<p>Unlike the `_progress` and `_report` handlers which verify worker UUID authentication, the `_log` handler does not gate on authentication.</p>
<p>### Proof of Concept</p>
<p>```bash
# Terminal 1: start the runner
echo '&lt;html&gt;&lt;body&gt;t&lt;/body&gt;&lt;/html&gt;' &gt; t.html
echo '{"username":"X","key":"X","test_path":"t.html","test_framework":"qunit","browsers":[]}' &gt; browserstack.json
node bin/runn…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-6vr3-7wcx-v5g5"/>
  </entry>
</feed>
