<?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>Tue, 06 Oct 2026 05:25:29 +0000</lastBuildDate>
    <item>
      <title>BIT-spark-2026-32773 — Apache Spark: XSS Vulnerability in Spark Web 3.5.4</title>
      <link>https://cve.radiocsirt.org/vuln/bit-spark-2026-32773</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: spark&lt;/p&gt;
&lt;p&gt;There is a lack of XSS escaping in the Spark History Server prior to 3.5.8 which allows a malicious Spark job to generate arbitrary unescaped frontend code which could lead to a minimal privilege escalation in browser. Users are encouraged to upgrade to Spark 3.5.8 or later.&lt;/p&gt;
&lt;p&gt;This CVE is marked as &amp;#34;low&amp;#34; since the path to exploit requires both relatively high permissions (ability to launch a Spark job) and requires tricking a user with higher permissions to log in and visit the Spark history web page.&lt;/p&gt;
&lt;p&gt;Users are encouraged to upgrade their Spark history servers to Spark 3.5.8 or later.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: spark&lt;/p&gt;
&lt;p&gt;There is a lack of XSS escaping in the Spark History Server prior to 3.5.8 which allows a malicious Spark job to generate arbitrary unescaped frontend code which could lead to a minimal privilege escalation in browser. Users are encouraged to upgrade to Spark 3.5.8 or later.&lt;/p&gt;
&lt;p&gt;This CVE is marked as &amp;#34;low&amp;#34; since the path to exploit requires both relatively high permissions (ability to launch a Spark job) and requires tricking a user with higher permissions to log in and visit the Spark history web page.&lt;/p&gt;
&lt;p&gt;Users are encouraged to upgrade their Spark history servers to Spark 3.5.8 or later.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bit-spark-2026-32773</guid>
    </item>
    <item>
      <title>EUVD-2026-362938</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-362938</link>
      <description>EUVD-2026-362938</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-362938</guid>
    </item>
    <item>
      <title>fkie_cve-2026-32773</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-32773</link>
      <description>&lt;p&gt;There is a lack of XSS escaping in the Spark History Server prior to 3.5.8 which allows a malicious Spark job to generate arbitrary unescaped frontend code which could lead to a minimal privilege escalation in browser. Users are encouraged to upgrade to Spark 3.5.8 or later.&lt;/p&gt;
&lt;p&gt;This CVE is marked as &amp;#34;low&amp;#34; since the path to exploit requires both relatively high permissions (ability to launch a Spark job) and requires tricking a user with higher permissions to log in and visit the Spark history web page.&lt;/p&gt;
&lt;p&gt;Users are encouraged to upgrade their Spark history servers to Spark 3.5.8 or later.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;There is a lack of XSS escaping in the Spark History Server prior to 3.5.8 which allows a malicious Spark job to generate arbitrary unescaped frontend code which could lead to a minimal privilege escalation in browser. Users are encouraged to upgrade to Spark 3.5.8 or later.&lt;/p&gt;
&lt;p&gt;This CVE is marked as &amp;#34;low&amp;#34; since the path to exploit requires both relatively high permissions (ability to launch a Spark job) and requires tricking a user with higher permissions to log in and visit the Spark history web page.&lt;/p&gt;
&lt;p&gt;Users are encouraged to upgrade their Spark history servers to Spark 3.5.8 or later.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-32773</guid>
    </item>
    <item>
      <title>GHSA-9437-39hj-3c93 — Apache Spark History Server allows stored cross-site scripting through unescaped application names</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9437-39hj-3c93</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: pyspark, Maven: org.apache.spark:spark-core_2.12, Maven: org.apache.spark:spark-core_2.13&lt;/p&gt;
&lt;p&gt;There is a lack of XSS escaping in the Spark History Server prior to 3.5.8 which allows a malicious Spark job to generate arbitrary unescaped frontend code which could lead to a minimal privilege escalation in browser. Users are encouraged to upgrade to Spark 3.5.8 or later.&lt;/p&gt;
&lt;p&gt;This CVE is marked as &amp;#34;low&amp;#34; since the path to exploit requires both relatively high permissions (ability to launch a Spark job) and requires tricking a user with higher permissions to log in and visit the Spark history web page.&lt;/p&gt;
&lt;p&gt;Users are encouraged to upgrade their Spark history servers to Spark 3.5.8 or later.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: pyspark, Maven: org.apache.spark:spark-core_2.12, Maven: org.apache.spark:spark-core_2.13&lt;/p&gt;
&lt;p&gt;There is a lack of XSS escaping in the Spark History Server prior to 3.5.8 which allows a malicious Spark job to generate arbitrary unescaped frontend code which could lead to a minimal privilege escalation in browser. Users are encouraged to upgrade to Spark 3.5.8 or later.&lt;/p&gt;
&lt;p&gt;This CVE is marked as &amp;#34;low&amp;#34; since the path to exploit requires both relatively high permissions (ability to launch a Spark job) and requires tricking a user with higher permissions to log in and visit the Spark history web page.&lt;/p&gt;
&lt;p&gt;Users are encouraged to upgrade their Spark history servers to Spark 3.5.8 or later.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9437-39hj-3c93</guid>
    </item>
    <item>
      <title>PYSEC-2026-3966</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-3966</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: pyspark&lt;/p&gt;
&lt;p&gt;There is a lack of XSS escaping in the Spark History Server prior to 3.5.8 which allows a malicious Spark job to generate arbitrary unescaped frontend code which could lead to a minimal privilege escalation in browser. Users are encouraged to upgrade to Spark 3.5.8 or later.&lt;/p&gt;
&lt;p&gt;This CVE is marked as &amp;#34;low&amp;#34; since the path to exploit requires both relatively high permissions (ability to launch a Spark job) and requires tricking a user with higher permissions to log in and visit the Spark history web page.&lt;/p&gt;
&lt;p&gt;Users are encouraged to upgrade their Spark history servers to Spark 3.5.8 or later.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: pyspark&lt;/p&gt;
&lt;p&gt;There is a lack of XSS escaping in the Spark History Server prior to 3.5.8 which allows a malicious Spark job to generate arbitrary unescaped frontend code which could lead to a minimal privilege escalation in browser. Users are encouraged to upgrade to Spark 3.5.8 or later.&lt;/p&gt;
&lt;p&gt;This CVE is marked as &amp;#34;low&amp;#34; since the path to exploit requires both relatively high permissions (ability to launch a Spark job) and requires tricking a user with higher permissions to log in and visit the Spark history web page.&lt;/p&gt;
&lt;p&gt;Users are encouraged to upgrade their Spark history servers to Spark 3.5.8 or later.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-3966</guid>
    </item>
  </channel>
</rss>
