<?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>Fri, 02 Oct 2026 19:42:19 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-180561</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-180561</link>
      <description>EUVD-2026-180561</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-180561</guid>
    </item>
    <item>
      <title>fkie_cve-2020-7729</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2020-7729</link>
      <description>&lt;p&gt;The package grunt before 1.3.0 are vulnerable to Arbitrary Code Execution due to the default usage of the function load() instead of its secure replacement safeLoad() of the package js-yaml inside grunt.file.readYAML.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The package grunt before 1.3.0 are vulnerable to Arbitrary Code Execution due to the default usage of the function load() instead of its secure replacement safeLoad() of the package js-yaml inside grunt.file.readYAML.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2020-7729</guid>
    </item>
    <item>
      <title>GHSA-m5pj-vjjf-4m3h — Arbitrary Code Execution in grunt</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-m5pj-vjjf-4m3h</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: grunt&lt;/p&gt;
&lt;p&gt;The package grunt before 1.3.0 are vulnerable to Arbitrary Code Execution due to the default usage of the function load() instead of its secure replacement safeLoad() of the package js-yaml inside grunt.file.readYAML.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: grunt&lt;/p&gt;
&lt;p&gt;The package grunt before 1.3.0 are vulnerable to Arbitrary Code Execution due to the default usage of the function load() instead of its secure replacement safeLoad() of the package js-yaml inside grunt.file.readYAML.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-m5pj-vjjf-4m3h</guid>
    </item>
    <item>
      <title>gsd-2020-7729</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2020-7729</link>
      <description>gsd-2020-7729</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2020-7729</guid>
    </item>
    <item>
      <title>OESA-2022-1544 — nodejs-grunt security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2022-1544</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP1: nodejs-grunt, openEuler:20.03-LTS-SP2: nodejs-grunt, openEuler:20.03-LTS-SP3: nodejs-grunt&lt;/p&gt;
&lt;p&gt;Grunt is the JavaScript task runner. Why use a task runner? In one word: automation. The less work you have to do when performing repetitive tasks like minification, compilation, unit testing, linting, etc, the easier your job becomes. After you&amp;amp;apos;ve configured it, a task runner can do most of that mundane work for you with basically zero effort.&#13;
&#13;
Security Fix(es):&#13;
&#13;
The package grunt before 1.3.0 are vulnerable to Arbitrary Code Execution due to the default usage of the function load() instead of its secure replacement safeLoad() of the package js-yaml inside grunt.file.readYAML.(CVE-2020-7729)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP1: nodejs-grunt, openEuler:20.03-LTS-SP2: nodejs-grunt, openEuler:20.03-LTS-SP3: nodejs-grunt&lt;/p&gt;
&lt;p&gt;Grunt is the JavaScript task runner. Why use a task runner? In one word: automation. The less work you have to do when performing repetitive tasks like minification, compilation, unit testing, linting, etc, the easier your job becomes. After you&amp;amp;apos;ve configured it, a task runner can do most of that mundane work for you with basically zero effort.&#13;
&#13;
Security Fix(es):&#13;
&#13;
The package grunt before 1.3.0 are vulnerable to Arbitrary Code Execution due to the default usage of the function load() instead of its secure replacement safeLoad() of the package js-yaml inside grunt.file.readYAML.(CVE-2020-7729)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2022-1544</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2020-7729</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-7729</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:18.04:LTS: grunt, Ubuntu:Pro:20.04:LTS: grunt&lt;/p&gt;
&lt;p&gt;The package grunt before 1.3.0 are vulnerable to Arbitrary Code Execution due to the default usage of the function load() instead of its secure replacement safeLoad() of the package js-yaml inside grunt.file.readYAML.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:18.04:LTS: grunt, Ubuntu:Pro:20.04:LTS: grunt&lt;/p&gt;
&lt;p&gt;The package grunt before 1.3.0 are vulnerable to Arbitrary Code Execution due to the default usage of the function load() instead of its secure replacement safeLoad() of the package js-yaml inside grunt.file.readYAML.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-7729</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2460 — Atlassian Bamboo, Bitbucket, Confluence, Fisheye, Crucible, Jira und Jira Service Management: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2460</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Atlassian Bamboo, Bitbucket, Confluence, Fisheye, Crucible, Jira und Jira Service Management ausnutzen, um beliebigen Code auszuführen, erweiterte Berechtigungen zu erlangen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren, vertrauliche Informationen offenzulegen oder einen Denial-of-Service-Zustand auszulösen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Atlassian Bamboo, Bitbucket, Confluence, Fisheye, Crucible, Jira und Jira Service Management ausnutzen, um beliebigen Code auszuführen, erweiterte Berechtigungen zu erlangen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren, vertrauliche Informationen offenzulegen oder einen Denial-of-Service-Zustand auszulösen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2460</guid>
    </item>
  </channel>
</rss>
