https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 11:05:38 +0000 https://cve.radiocsirt.org/vuln/alsa-2025:21038 <p><strong>Affected:</strong> AlmaLinux:10: kea-doc</p> <p>DHCP implementation from Internet Systems Consortium, Inc. that features fully functional DHCPv4, DHCPv6 and Dynamic DNS servers. Both DHCP servers fully support server discovery, address assignment, renewal, rebinding and release. The DHCPv6 server supports prefix delegation. Both servers support DNS Update mechanism, using stand-alone DDNS daemon.</p> <p>Security Fix(es):</p> <p>* kea: Invalid characters cause assert (CVE-2025-11232)</p> <p>For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.</p> <p><strong>Affected:</strong> AlmaLinux:10: kea-doc</p> <p>DHCP implementation from Internet Systems Consortium, Inc. that features fully functional DHCPv4, DHCPv6 and Dynamic DNS servers. Both DHCP servers fully support server discovery, address assignment, renewal, rebinding and release. The DHCPv6 server supports prefix delegation. Both servers support DNS Update mechanism, using stand-alone DDNS daemon.</p> <p>Security Fix(es):</p> <p>* kea: Invalid characters cause assert (CVE-2025-11232)</p> <p>For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.</p> https://cve.radiocsirt.org/vuln/alsa-2025:21038 https://cve.radiocsirt.org/vuln/bdu:2025-15604 bdu:2025-15604 https://cve.radiocsirt.org/vuln/bdu:2025-15604 https://cve.radiocsirt.org/vuln/euvd-2026-259931 EUVD-2026-259931 https://cve.radiocsirt.org/vuln/euvd-2026-259931 https://cve.radiocsirt.org/vuln/fkie_cve-2025-11232 <p>To trigger the issue, three configuration parameters must have specific settings: &#34;hostname-char-set&#34; must be left at the default setting, which is &#34;[^A-Za-z0-9.-]&#34;; &#34;hostname-char-replacement&#34; must be empty (the default); and &#34;ddns-qualifying-suffix&#34; must *NOT* be empty (the default is empty). DDNS updates do not need to be enabled for this issue to manifest. A client that sends certain option content would then cause kea-dhcp4 to exit unexpectedly. This issue affects Kea versions 3.0.1 through 3.0.1 and 3.1.1 through 3.1.2.</p> <p>To trigger the issue, three configuration parameters must have specific settings: &#34;hostname-char-set&#34; must be left at the default setting, which is &#34;[^A-Za-z0-9.-]&#34;; &#34;hostname-char-replacement&#34; must be empty (the default); and &#34;ddns-qualifying-suffix&#34; must *NOT* be empty (the default is empty). DDNS updates do not need to be enabled for this issue to manifest. A client that sends certain option content would then cause kea-dhcp4 to exit unexpectedly. This issue affects Kea versions 3.0.1 through 3.0.1 and 3.1.1 through 3.1.2.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-11232 https://cve.radiocsirt.org/vuln/ghsa-wcxf-jmjh-x27q <p>To trigger the issue, three configuration parameters must have specific settings: &#34;hostname-char-set&#34; must be left at the default setting, which is &#34;[^A-Za-z0-9.-]&#34;; &#34;hostname-char-replacement&#34; must be empty (the default); and &#34;ddns-qualifying-suffix&#34; must *NOT* be empty (the default is empty). DDNS updates do not need to be enabled for this issue to manifest. A client that sends certain option content would then cause kea-dhcp4 to exit unexpectedly. This issue affects Kea versions 3.0.1 through 3.0.1 and 3.1.1 through 3.1.2.</p> <p>To trigger the issue, three configuration parameters must have specific settings: &#34;hostname-char-set&#34; must be left at the default setting, which is &#34;[^A-Za-z0-9.-]&#34;; &#34;hostname-char-replacement&#34; must be empty (the default); and &#34;ddns-qualifying-suffix&#34; must *NOT* be empty (the default is empty). DDNS updates do not need to be enabled for this issue to manifest. A client that sends certain option content would then cause kea-dhcp4 to exit unexpectedly. This issue affects Kea versions 3.0.1 through 3.0.1 and 3.1.1 through 3.1.2.</p> https://cve.radiocsirt.org/vuln/ghsa-wcxf-jmjh-x27q https://cve.radiocsirt.org/vuln/opensuse-su-2025:15677-1 <p>kea-3.0.2-1.1 on GA media</p> <p>kea-3.0.2-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2025:15677-1 https://cve.radiocsirt.org/vuln/suse-su-2026:20989-1 <p>Security update for kea</p> <p>Security update for kea</p> https://cve.radiocsirt.org/vuln/suse-su-2026:20989-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-11232 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: isc-kea, Ubuntu:Pro:18.04:LTS: isc-kea, Ubuntu:20.04:LTS: isc-kea, Ubuntu:22.04:LTS: isc-kea, Ubuntu:24.04:LTS: isc-kea, Ubuntu:25.10: isc-kea, Ubuntu:25.04: isc-kea</p> <p>To trigger the issue, three configuration parameters must have specific settings: &#34;hostname-char-set&#34; must be left at the default setting, which is &#34;[^A-Za-z0-9.-]&#34;; &#34;hostname-char-replacement&#34; must be empty (the default); and &#34;ddns-qualifying-suffix&#34; must *NOT* be empty (the default is empty). DDNS updates do not need to be enabled for this issue to manifest. A client that sends certain option content would then cause kea-dhcp4 to exit unexpectedly. This issue affects Kea versions 3.0.1 through 3.0.1 and 3.1.1 through 3.1.2.</p> <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: isc-kea, Ubuntu:Pro:18.04:LTS: isc-kea, Ubuntu:20.04:LTS: isc-kea, Ubuntu:22.04:LTS: isc-kea, Ubuntu:24.04:LTS: isc-kea, Ubuntu:25.10: isc-kea, Ubuntu:25.04: isc-kea</p> <p>To trigger the issue, three configuration parameters must have specific settings: &#34;hostname-char-set&#34; must be left at the default setting, which is &#34;[^A-Za-z0-9.-]&#34;; &#34;hostname-char-replacement&#34; must be empty (the default); and &#34;ddns-qualifying-suffix&#34; must *NOT* be empty (the default is empty). DDNS updates do not need to be enabled for this issue to manifest. A client that sends certain option content would then cause kea-dhcp4 to exit unexpectedly. This issue affects Kea versions 3.0.1 through 3.0.1 and 3.1.1 through 3.1.2.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-11232 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2568 <p>Ein Angreifer kann mehrere Schwachstellen in Red Hat Enterprise Linux ausnutzen, um einen Denial of Service Angriff durchzuführen.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Red Hat Enterprise Linux ausnutzen, um einen Denial of Service Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2568