<?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>Wed, 07 Oct 2026 06:14:43 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-225606</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-225606</link>
      <description>EUVD-2026-225606</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-225606</guid>
    </item>
    <item>
      <title>fkie_cve-2025-26619</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-26619</link>
      <description>&lt;p&gt;Vega is a visualization grammar, a declarative format for creating, saving, and sharing interactive visualization designs. In `vega` 5.30.0 and lower and in `vega-functions` 5.15.0 and lower , it was possible to call JavaScript functions from the Vega expression language that were not meant to be supported. The issue is patched in `vega` `5.31.0`  and `vega-functions` `5.16.0`. Some workarounds are available. Run `vega` without `vega.expressionInterpreter`. This mode is not the default as it is slower. Alternatively, using the interpreter described in CSP safe mode (Content Security Policy) prevents arbitrary Javascript from running, so users of this mode are not affected by this vulnerability.&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` 5.30.0 and lower and in `vega-functions` 5.15.0 and lower , it was possible to call JavaScript functions from the Vega expression language that were not meant to be supported. The issue is patched in `vega` `5.31.0`  and `vega-functions` `5.16.0`. Some workarounds are available. Run `vega` without `vega.expressionInterpreter`. This mode is not the default as it is slower. Alternatively, using the interpreter described in CSP safe mode (Content Security Policy) prevents arbitrary Javascript from running, so users of this mode are not affected by this vulnerability.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-26619</guid>
    </item>
    <item>
      <title>GHSA-rcw3-wmx7-cphr — Vega Cross-Site Scripting (XSS) via event filter when not using CSP mode expressionInterpeter</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-rcw3-wmx7-cphr</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;In `vega` 5.30.0 and lower,  `vega-functions` 5.15.0 and lower , it was possible to call JavaScript functions from the Vega expression language that were not meant to be supported.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Patched in `vega` `5.31.0`  / `vega-functions` `5.16.0`&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;_Is there a way for users to fix or remediate the vulnerability without upgrading?_&lt;/p&gt;
&lt;p&gt;- Run `vega` without `vega.expressionInterpreter`. This mode is not the default as it is slower. 
- Using the interpreter [described in CSP safe mode](https://vega.github.io/vega/usage/interpreter/) (Content Security Policy) prevents arbitrary Javascript from running, so users of this mode are not affected by this vulnerability.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;- Reported to Vega-Lite by @kprevas Nov 8 2024 in https://github.com/vega/vega-lite/issues/9469 &amp;amp;  https://github.com/vega/vega/issues/3984&lt;/p&gt;
&lt;p&gt;Reproduction of the error in Vega by @mattijn&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;inject_alert&amp;#34;,
      &amp;#34;on&amp;#34;: [
        {
          &amp;#34;events&amp;#34;: [
            {
              &amp;#34;type&amp;#34;: &amp;#34;mousedown&amp;#34;,
              &amp;#34;marktype&amp;#34;: &amp;#34;rect&amp;#34;,
              &amp;#34;filter&amp;#34;: [&amp;#34;scale(event.view.setTimeout, &amp;#39;alert(\&amp;#34;alert\&amp;#34;)&amp;#39;)&amp;#34;]
            }
          ],
          &amp;#34;update&amp;#34;: &amp;#34;datum&amp;#34;
        }
      ]
    }
  ],
  &amp;#34;marks&amp;#34;: [
    {
      &amp;#34;type&amp;#34;: &amp;#34;rect&amp;#34;,
      &amp;#34;encode&amp;#34;: {
        &amp;#34;update&amp;#34;: {
          &amp;#34;x&amp;#34;: {&amp;#34;value&amp;#34;: 0},
          &amp;#34;y&amp;#34;: {&amp;#34;value&amp;#34;: 0},
          &amp;#34;width&amp;#34;: {&amp;#34;value&amp;#34;: 100},
          &amp;#34;height&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;In `vega` 5.30.0 and lower,  `vega-functions` 5.15.0 and lower , it was possible to call JavaScript functions from the Vega expression language that were not meant to be supported.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Patched in `vega` `5.31.0`  / `vega-functions` `5.16.0`&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;_Is there a way for users to fix or remediate the vulnerability without upgrading?_&lt;/p&gt;
&lt;p&gt;- Run `vega` without `vega.expressionInterpreter`. This mode is not the default as it is slower. 
- Using the interpreter [described in CSP safe mode](https://vega.github.io/vega/usage/interpreter/) (Content Security Policy) prevents arbitrary Javascript from running, so users of this mode are not affected by this vulnerability.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;- Reported to Vega-Lite by @kprevas Nov 8 2024 in https://github.com/vega/vega-lite/issues/9469 &amp;amp;  https://github.com/vega/vega/issues/3984&lt;/p&gt;
&lt;p&gt;Reproduction of the error in Vega by @mattijn&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;inject_alert&amp;#34;,
      &amp;#34;on&amp;#34;: [
        {
          &amp;#34;events&amp;#34;: [
            {
              &amp;#34;type&amp;#34;: &amp;#34;mousedown&amp;#34;,
              &amp;#34;marktype&amp;#34;: &amp;#34;rect&amp;#34;,
              &amp;#34;filter&amp;#34;: [&amp;#34;scale(event.view.setTimeout, &amp;#39;alert(\&amp;#34;alert\&amp;#34;)&amp;#39;)&amp;#34;]
            }
          ],
          &amp;#34;update&amp;#34;: &amp;#34;datum&amp;#34;
        }
      ]
    }
  ],
  &amp;#34;marks&amp;#34;: [
    {
      &amp;#34;type&amp;#34;: &amp;#34;rect&amp;#34;,
      &amp;#34;encode&amp;#34;: {
        &amp;#34;update&amp;#34;: {
          &amp;#34;x&amp;#34;: {&amp;#34;value&amp;#34;: 0},
          &amp;#34;y&amp;#34;: {&amp;#34;value&amp;#34;: 0},
          &amp;#34;width&amp;#34;: {&amp;#34;value&amp;#34;: 100},
          &amp;#34;height&amp;#34;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-rcw3-wmx7-cphr</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-26619</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-26619</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` 5.30.0 and lower and in `vega-functions` 5.15.0 and lower , it was possible to call JavaScript functions from the Vega expression language that were not meant to be supported. The issue is patched in `vega` `5.31.0`  and `vega-functions` `5.16.0`. Some workarounds are available. Run `vega` without `vega.expressionInterpreter`. This mode is not the default as it is slower. Alternatively, using the interpreter described in CSP safe mode (Content Security Policy) prevents arbitrary Javascript from running, so users of this mode are not affected by this vulnerability.&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` 5.30.0 and lower and in `vega-functions` 5.15.0 and lower , it was possible to call JavaScript functions from the Vega expression language that were not meant to be supported. The issue is patched in `vega` `5.31.0`  and `vega-functions` `5.16.0`. Some workarounds are available. Run `vega` without `vega.expressionInterpreter`. This mode is not the default as it is slower. Alternatively, using the interpreter described in CSP safe mode (Content Security Policy) prevents arbitrary Javascript from running, so users of this mode are not affected by this vulnerability.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-26619</guid>
    </item>
  </channel>
</rss>
