<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-08T15:50:26.251502+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bit-spark-2021-38296</id>
    <title>BIT-spark-2021-38296 — Apache Spark Key Negotiation Vulnerability</title>
    <updated>2026-10-08T15:50:26.259887+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: spark</p>
<p>Apache Spark supports end-to-end encryption of RPC connections via "spark.authenticate" and "spark.network.crypto.enabled". In versions 3.1.2 and earlier, it uses a bespoke mutual authentication protocol that allows for full encryption key recovery. After an initial interactive attack, this would allow someone to decrypt plaintext traffic offline. Note that this does not affect security mechanisms controlled by "spark.authenticate.enableSaslEncryption", "spark.io.encryption.enabled", "spark.ssl", "spark.ui.strictTransportSecurity". Update to Apache Spark 3.1.3 or later</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bit-spark-2021-38296"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1165</id>
    <title>certfr-2026-avi-1165 — De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre elles permettent à un attaquan…</title>
    <updated>2026-10-08T15:50:26.259944+00:00</updated>
    <content>certfr-2026-avi-1165</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2026-avi-1165"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cnvd-2022-21823</id>
    <title>cnvd-2022-21823</title>
    <updated>2026-10-08T15:50:26.259964+00:00</updated>
    <content>cnvd-2022-21823</content>
    <link href="https://cve.radiocsirt.org/vuln/cnvd-2022-21823"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-30215</id>
    <title>EUVD-2026-30215</title>
    <updated>2026-10-08T15:50:26.259977+00:00</updated>
    <content>EUVD-2026-30215</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-30215"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2021-38296</id>
    <title>fkie_cve-2021-38296</title>
    <updated>2026-10-08T15:50:26.259987+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Apache Spark supports end-to-end encryption of RPC connections via "spark.authenticate" and "spark.network.crypto.enabled". In versions 3.1.2 and earlier, it uses a bespoke mutual authentication protocol that allows for full encryption key recovery. After an initial interactive attack, this would allow someone to decrypt plaintext traffic offline. Note that this does not affect security mechanisms controlled by "spark.authenticate.enableSaslEncryption", "spark.io.encryption.enabled", "spark.ssl", "spark.ui.strictTransportSecurity". Update to Apache Spark 3.1.3 or later</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2021-38296"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-9rr6-jpg7-9jg6</id>
    <title>GHSA-9rr6-jpg7-9jg6 — Authentication Bypass by Capture-replay in Apache Spark</title>
    <updated>2026-10-08T15:50:26.260012+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Maven: org.apache.spark:spark-core, PyPI: pyspark</p>
<p>Apache Spark supports end-to-end encryption of RPC connections via "spark.authenticate" and "spark.network.crypto.enabled". In versions 3.1.2 and earlier, it uses a bespoke mutual authentication protocol that allows for full encryption key recovery. After an initial interactive attack, this would allow someone to decrypt plaintext traffic offline. Note that this does not affect security mechanisms controlled by "spark.authenticate.enableSaslEncryption", "spark.io.encryption.enabled", "spark.ssl", "spark.ui.strictTransportSecurity". Update to Apache Spark 3.1.3 or later</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-9rr6-jpg7-9jg6"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2021-38296</id>
    <title>gsd-2021-38296</title>
    <updated>2026-10-08T15:50:26.260037+00:00</updated>
    <content>gsd-2021-38296</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2021-38296"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/oesa-2022-1591</id>
    <title>OESA-2022-1591 — spark security update</title>
    <updated>2026-10-08T15:50:26.260048+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:20.03-LTS-SP1: spark, openEuler:20.03-LTS-SP2: spark, openEuler:20.03-LTS-SP3: spark</p>
<p>Apache Spark achieves high performance for both batch and streaming data, using a state-of-the-art DAG scheduler, a query optimizer, and a physical execution engine.

Security Fix(es):

Apache Spark supports end-to-end encryption of RPC connections via &amp;quot;spark.authenticate&amp;quot; and &amp;quot;spark.network.crypto.enabled&amp;quot;. In versions 3.1.2 and earlier, it uses a bespoke mutual authentication protocol that allows for full encryption key recovery. After an initial interactive attack, this would allow someone to decrypt plaintext traffic offline. Note that this does not affect security mechanisms controlled by &amp;quot;spark.authenticate.enableSaslEncryption&amp;quot;, &amp;quot;spark.io.encryption.enabled&amp;quot;, &amp;quot;spark.ssl&amp;quot;, &amp;quot;spark.ui.strictTransportSecurity&amp;quot;. Update to Apache Spark 3.1.3 or later(CVE-2021-38296)</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/oesa-2022-1591"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/pysec-2022-186</id>
    <title>PYSEC-2022-186</title>
    <updated>2026-10-08T15:50:26.260075+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: pyspark</p>
<p>Apache Spark supports end-to-end encryption of RPC connections via "spark.authenticate" and "spark.network.crypto.enabled". In versions 3.1.2 and earlier, it uses a bespoke mutual authentication protocol that allows for full encryption key recovery. After an initial interactive attack, this would allow someone to decrypt plaintext traffic offline. Note that this does not affect security mechanisms controlled by "spark.authenticate.enableSaslEncryption", "spark.io.encryption.enabled", "spark.ssl", "spark.ui.strictTransportSecurity". Update to Apache Spark 3.1.3 or later</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/pysec-2022-186"/>
  </entry>
</feed>
