<?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>Thu, 15 Oct 2026 23:00:35 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-250296</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-250296</link>
      <description>EUVD-2026-250296</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-250296</guid>
    </item>
    <item>
      <title>fkie_cve-2025-55164</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-55164</link>
      <description>&lt;p&gt;content-security-policy-parser parses content security policy directives. A prototype pollution vulnerability exists in versions 0.5.0 and earlier, wherein if a policy name is called __proto__, one can override the Object prototype. This issue has been patched in version 0.6.0. A workaround involves disabling prototype method in NodeJS, neutralizing all possible prototype pollution attacks. Provide either --disable-proto=delete (recommended) or --disable-proto=throw as an argument to node to enable this feature.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;content-security-policy-parser parses content security policy directives. A prototype pollution vulnerability exists in versions 0.5.0 and earlier, wherein if a policy name is called __proto__, one can override the Object prototype. This issue has been patched in version 0.6.0. A workaround involves disabling prototype method in NodeJS, neutralizing all possible prototype pollution attacks. Provide either --disable-proto=delete (recommended) or --disable-proto=throw as an argument to node to enable this feature.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-55164</guid>
    </item>
    <item>
      <title>GHSA-w2cq-g8g3-gm83 — content-security-policy-parser Prototype Pollution Vulnerability May Lead to RCE</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-w2cq-g8g3-gm83</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: content-security-policy-parser&lt;/p&gt;
&lt;p&gt;### Impact
A prototype pollution vulnerability exists in versions 0.5.0 and earlier, wherein if you provide a policy name called `__proto__` you can override the Object prototype.&lt;/p&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p&gt;```
const parse = require(&amp;#39;content-security-policy-parser&amp;#39;);&lt;/p&gt;
&lt;p&gt;const x = parse(&amp;#34;default-src &amp;#39;self&amp;#39;; __proto__ foobar&amp;#34;);
console.log(&amp;#39;raw print:&amp;#39;, x);
console.log(&amp;#39;toString:&amp;#39;, x.toString());
```&lt;/p&gt;
&lt;p&gt;Outputs:&lt;/p&gt;
&lt;p&gt;```
raw print: Array { &amp;#39;default-src&amp;#39;: [ &amp;#34;&amp;#39;self&amp;#39;&amp;#34; ] }
toString: foobar
```&lt;/p&gt;
&lt;p&gt;Whilst no gadget exists in this library, it is possible via other libraries expose functionality that enable RCE. It is customary to label prototype pollution vulnerabilities in this way. The most common effect of this is denial of service, as you can trivially overwrite properties.&lt;/p&gt;
&lt;p&gt;As the content security policy is provided in HTTP queries, it is incredibly likely that network exploitation is possible.&lt;/p&gt;
&lt;p&gt;### Patches
There has been a patch implemented a year ago (11 Feb 2024), but low uptake of patched versions has not been observed in the wild - only 17% of weekly downloads are of patched versions.&lt;/p&gt;
&lt;p&gt;### Workarounds
By disabling prototype method in NodeJS you can neutralise all possible prototype pollution attacks. Provide either `--disable-proto=delete` (recommended) or `--disable-proto=throw` as an argument to `node` to enable this feature.&lt;/p&gt;
&lt;p&gt;### References
[Issue revealing the problem, January 26 2024](https://github.com/helmetjs/content-security-policy-parser/issues/11)
[Commit fixing the problem](https://g…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: content-security-policy-parser&lt;/p&gt;
&lt;p&gt;### Impact
A prototype pollution vulnerability exists in versions 0.5.0 and earlier, wherein if you provide a policy name called `__proto__` you can override the Object prototype.&lt;/p&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p&gt;```
const parse = require(&amp;#39;content-security-policy-parser&amp;#39;);&lt;/p&gt;
&lt;p&gt;const x = parse(&amp;#34;default-src &amp;#39;self&amp;#39;; __proto__ foobar&amp;#34;);
console.log(&amp;#39;raw print:&amp;#39;, x);
console.log(&amp;#39;toString:&amp;#39;, x.toString());
```&lt;/p&gt;
&lt;p&gt;Outputs:&lt;/p&gt;
&lt;p&gt;```
raw print: Array { &amp;#39;default-src&amp;#39;: [ &amp;#34;&amp;#39;self&amp;#39;&amp;#34; ] }
toString: foobar
```&lt;/p&gt;
&lt;p&gt;Whilst no gadget exists in this library, it is possible via other libraries expose functionality that enable RCE. It is customary to label prototype pollution vulnerabilities in this way. The most common effect of this is denial of service, as you can trivially overwrite properties.&lt;/p&gt;
&lt;p&gt;As the content security policy is provided in HTTP queries, it is incredibly likely that network exploitation is possible.&lt;/p&gt;
&lt;p&gt;### Patches
There has been a patch implemented a year ago (11 Feb 2024), but low uptake of patched versions has not been observed in the wild - only 17% of weekly downloads are of patched versions.&lt;/p&gt;
&lt;p&gt;### Workarounds
By disabling prototype method in NodeJS you can neutralise all possible prototype pollution attacks. Provide either `--disable-proto=delete` (recommended) or `--disable-proto=throw` as an argument to `node` to enable this feature.&lt;/p&gt;
&lt;p&gt;### References
[Issue revealing the problem, January 26 2024](https://github.com/helmetjs/content-security-policy-parser/issues/11)
[Commit fixing the problem](https://g…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-w2cq-g8g3-gm83</guid>
    </item>
  </channel>
</rss>
