https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 01:50:47 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-09403 bdu:2026-09403 https://cve.radiocsirt.org/vuln/bdu:2026-09403 https://cve.radiocsirt.org/vuln/bit-kafka-2026-33557 <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> <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> https://cve.radiocsirt.org/vuln/bit-kafka-2026-33557 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0461 certfr-2026-avi-0461 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0461 https://cve.radiocsirt.org/vuln/cleanstart-2026-ad78101 <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> <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> https://cve.radiocsirt.org/vuln/cleanstart-2026-ad78101 https://cve.radiocsirt.org/vuln/euvd-2026-337334 EUVD-2026-337334 https://cve.radiocsirt.org/vuln/euvd-2026-337334 https://cve.radiocsirt.org/vuln/fkie_cve-2026-33557 <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> <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> https://cve.radiocsirt.org/vuln/fkie_cve-2026-33557 https://cve.radiocsirt.org/vuln/ghsa-28jg-cgg7-j4wc <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> <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> https://cve.radiocsirt.org/vuln/ghsa-28jg-cgg7-j4wc https://cve.radiocsirt.org/vuln/ncsc-2026-0254 NCSC-2026-0254 https://cve.radiocsirt.org/vuln/ncsc-2026-0254 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-33557 <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> <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> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-33557 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1166 <p>Ein Angreifer kann mehrere Schwachstellen in Apache Kafka ausnutzen, um Sicherheitsvorkehrungen zu umgehen, und um Informationen offenzulegen.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Apache Kafka ausnutzen, um Sicherheitsvorkehrungen zu umgehen, und um Informationen offenzulegen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1166