<?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-06T07:14:00.736091+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-280391</id>
    <title>EUVD-2026-280391</title>
    <updated>2026-10-06T07:14:00.802068+00:00</updated>
    <content>EUVD-2026-280391</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-280391"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-34217</id>
    <title>fkie_cve-2026-34217</title>
    <updated>2026-10-06T07:14:00.802108+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>SandboxJS is a JavaScript sandboxing library. Prior to 0.8.36, a scope modification vulnerability exists in @nyariv/sandboxjs. The vulnerability allows untrusted sandboxed code to leak internal interpreter objects through the new operator, exposing sandbox scope objects in the scope hierarchy to untrusted code; an unexpected and undesired exploit. While this could allow modifying scopes inside the sandbox, code evaluation remains sandboxed and prototypes remain protected throughout the execution. This vulnerability is fixed in 0.8.36.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-34217"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-hg73-4w7g-q96w</id>
    <title>GHSA-hg73-4w7g-q96w — SandboxJS: Sandbox Escape via Prop Object Leak in New Handler</title>
    <updated>2026-10-06T07:14:00.802144+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: @nyariv/sandboxjs</p>
<p>## Description</p>
<p>A scope modification vulnerability exists in `@nyariv/sandboxjs` version 0.8.35 and below. The vulnerability allows untrusted sandboxed code to leak internal interpreter objects through the `new` operator, exposing sandbox scope objects in the scope hierarchy to untrusted code; an unexpected and undesired exploit. While this could allow modifying scopes inside the sandbox, code evaluation remains sandboxed and prototypes remain protected throughout the execution.</p>
<p>## Vulnerable Code Location</p>
<p>### Primary: The `New` Operator Handler</p>
<p>**File**: `src/executor.ts`, lines 1275–1280</p>
<p>```typescript
addOps&lt;new (...args: unknown[]) =&gt; unknown, unknown[]&gt;(
  LispType.New,
  ({ done, a, b, context }) =&gt; {
    if (!context.ctx.globalsWhitelist.has(a) &amp;&amp; !context.ctx.sandboxedFunctions.has(a)) {
      throw new SandboxAccessError(`Object construction not allowed: ${a.constructor.name}`);
    }
    done(undefined, new a(...b));  // ← b is NOT sanitized, return is NOT sanitized
  },
);
```</p>
<p>This handler has **two missing sanitization steps**:</p>
<p>1. **Arguments (`b`) are not passed through `valueOrProp()`** — Constructor arguments contain raw `Prop` objects (internal interpreter wrappers) instead of extracted values.</p>
<p>2. **Return value is not passed through `getGlobalProp()` or `sanitizeArray()`** — The constructed object is returned directly to the execution tree without any sanitization.</p>
<p>### Comparison: The `Call` Handler (Correctly Implemented)</p>
<p>**File**: `src/executor.ts`…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-hg73-4w7g-q96w"/>
  </entry>
</feed>
