<?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-03T04:28:51.237887+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/bdu:2026-09403</id>
    <title>bdu:2026-09403</title>
    <updated>2026-10-03T04:28:51.392489+00:00</updated>
    <content>bdu:2026-09403</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2026-09403"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bit-kafka-2026-33557</id>
    <title>BIT-kafka-2026-33557 — Apache Kafka: Missing JWT token validation in OAUTHBEARER authentication</title>
    <updated>2026-10-03T04:28:51.392525+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: kafka</p>
<p>A possible security vulnerability has been identified in Apache Kafka.</p>
<p>By default, the broker property `sasl.oauthbearer.jwt.validator.class` is set to `org.apache.kafka.common.security.oauthbearer.DefaultJwtValidator`. It accepts any JWT token without validating its signature, issuer, or audience. An attacker can generate a JWT token from any issuer with the `preferred_username` set to any user, and the broker will accept it.</p>
<p>We advise the Kafka users using kafka v4.1.0 or v4.1.1 to set the config `sasl.oauthbearer.jwt.validator.class` to `org.apache.kafka.common.security.oauthbearer.BrokerJwtValidator` explicitly to avoid this vulnerability. Since Kafka v4.1.2 and v4.2.0 and later, the issue is fixed and will correctly validate the JWT token.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bit-kafka-2026-33557"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0461</id>
    <title>certfr-2026-avi-0461 — De multiples vulnérabilités ont été découvertes dans Apache Kafka. Elles permettent à un attaquant de provoquer une att…</title>
    <updated>2026-10-03T04:28:51.392564+00:00</updated>
    <content>certfr-2026-avi-0461</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2026-avi-0461"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cleanstart-2026-ad78101</id>
    <title>CLEANSTART-2026-AD78101 — Security fix for CVE-2026-33557 applied in: apache-nifi 2.7.2-r7</title>
    <updated>2026-10-03T04:28:51.392581+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> CleanStart: apache-nifi</p>
<p>Security vulnerability affects the apache-nifi package. This issue is resolved in later releases. See references for vulnerability details.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cleanstart-2026-ad78101"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-337334</id>
    <title>EUVD-2026-337334</title>
    <updated>2026-10-03T04:28:51.392599+00:00</updated>
    <content>EUVD-2026-337334</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-337334"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-33557</id>
    <title>fkie_cve-2026-33557</title>
    <updated>2026-10-03T04:28:51.392610+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>A possible security vulnerability has been identified in Apache Kafka.</p>
<p>By default, the broker property `sasl.oauthbearer.jwt.validator.class` is set to `org.apache.kafka.common.security.oauthbearer.DefaultJwtValidator`. It accepts any JWT token without validating its signature, issuer, or audience. An attacker can generate a JWT token from any issuer with the `preferred_username` set to any user, and the broker will accept it.</p>
<p>We advise the Kafka users using kafka v4.1.0 or v4.1.1 to set the config `sasl.oauthbearer.jwt.validator.class` to `org.apache.kafka.common.security.oauthbearer.BrokerJwtValidator` explicitly to avoid this vulnerability. Since Kafka v4.1.2 and v4.2.0 and later, the issue is fixed and will correctly validate the JWT token.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-33557"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-28jg-cgg7-j4wc</id>
    <title>GHSA-28jg-cgg7-j4wc — Apache Kafka does not validate JWT tokens in its OAUTHBEARER authentication implementation</title>
    <updated>2026-10-03T04:28:51.392635+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Maven: org.apache.kafka:kafka-clients</p>
<p>A security vulnerability has been identified in Apache Kafka. By default, the broker property `sasl.oauthbearer.jwt.validator.class` is set to `org.apache.kafka.common.security.oauthbearer.DefaultJwtValidator`. It accepts any JWT token without validating its signature, issuer, or audience. An attacker can generate a JWT token from any issuer with the `preferred_username` set to any user, and the broker will accept it.</p>
<p>Apache advises Kafka users using kafka v4.1.0 or v4.1.1 to set the config `sasl.oauthbearer.jwt.validator.class` to `org.apache.kafka.common.security.oauthbearer.BrokerJwtValidator` explicitly to avoid this vulnerability. Since Kafka v4.1.2 and v4.2.0 and later, the issue is fixed and will correctly validate the JWT token.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-28jg-cgg7-j4wc"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ncsc-2026-0254</id>
    <title>NCSC-2026-0254 — Kwetsbaarheden verholpen in Oracle database producten</title>
    <updated>2026-10-03T04:28:51.392657+00:00</updated>
    <content>NCSC-2026-0254</content>
    <link href="https://cve.radiocsirt.org/vuln/ncsc-2026-0254"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-33557</id>
    <title>UBUNTU-CVE-2026-33557</title>
    <updated>2026-10-03T04:28:51.392677+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:18.04:LTS: kafka</p>
<p>A possible security vulnerability has been identified in Apache Kafka. By default, the broker property `sasl.oauthbearer.jwt.validator.class` is set to `org.apache.kafka.common.security.oauthbearer.DefaultJwtValidator`. It accepts any JWT token without validating its signature, issuer, or audience. An attacker can generate a JWT token from any issuer with the `preferred_username` set to any user, and the broker will accept it. We advise the Kafka users using kafka v4.1.0 or v4.1.1 to set the config `sasl.oauthbearer.jwt.validator.class` to `org.apache.kafka.common.security.oauthbearer.BrokerJwtValidator` explicitly to avoid this vulnerability. Since Kafka v4.1.2 and v4.2.0 and later, the issue is fixed and will correctly validate the JWT token.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-33557"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1166</id>
    <title>WID-SEC-W-2026-1166 — Apache Kafka: Mehrere Schwachstellen</title>
    <updated>2026-10-03T04:28:51.392697+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen in Apache Kafka ausnutzen, um Sicherheitsvorkehrungen zu umgehen, und um Informationen offenzulegen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1166"/>
  </entry>
</feed>
