https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-02T20:52:32.596459+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bell-cve-2026-19941 BELL-CVE-2026-19941 2026-10-02T20:52:32.608094+00:00

Affected: Alpaquita:23: bind, Alpaquita:25: bind, Alpaquita:stream: bind

 https://cve.radiocsirt.org/vuln/euvd-2026-371416 EUVD-2026-371416 2026-10-02T20:52:32.608159+00:00 EUVD-2026-371416 https://cve.radiocsirt.org/vuln/fkie_cve-2026-19941 fkie_cve-2026-19941 2026-10-02T20:52:32.608186+00:00

An inapplicable NSEC record may be accepted by a `named` resolver as proof that no wildcard exists, which could allow an attacker at the same or an upstream level of the zone name to mask the existence of a victim's wildcard record. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.

 https://cve.radiocsirt.org/vuln/ghsa-38fx-cm5x-27pg GHSA-38fx-cm5x-27pg 2026-10-02T20:52:32.608230+00:00

An inapplicable NSEC record may be accepted by a `named` resolver as proof that no wildcard exists, which could allow an attacker at the same or an upstream level of the zone name to mask the existence of a victim's wildcard record. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.

 https://cve.radiocsirt.org/vuln/msrc_cve-2026-19941 msrc_CVE-2026-19941 — checkwildcard() accepts an out-of-zone NSEC as a wildcard-nonexistence proof 2026-10-02T20:52:32.608262+00:00 msrc_CVE-2026-19941 https://cve.radiocsirt.org/vuln/opensuse-su-2026:11916-1 openSUSE-SU-2026:11916-1 — bind-9.20.29-1.1 on GA media 2026-10-02T20:52:32.608292+00:00

bind-9.20.29-1.1 on GA media

 https://cve.radiocsirt.org/vuln/rhsa-2026:68279 RHSA-2026:68279 — Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update 2026-10-02T20:52:32.608329+00:00

bind: BIND: Unauthorized zone content updates via unauthenticated IXFR deltas bind9: bind: BIND 9: Denial of Service via crafted DNSSEC responses bind: BIND: Denial of Service via malformed DNS64 responses bind9: bind: BIND 9: Denial of Service via 16-bit length truncation in DNS negative cache handling bind: BIND: Denial of Service via invalid DNSSEC records bind9: bind: BIND 9: DNS wildcard record existence can be masked by an attacker via inapplicable NSEC records bind: BIND 9: Denial of Service via crafted query responses bind: BIND: Denial of Service via TKEY query with specific configuration bind9: bind: BIND 9: DNSSEC bypass via NSEC3 insecure-referral proof bind: BIND: Remote Denial of Service via crafted DNS-over-HTTPS request bind: BIND: DNS cache poisoning via malformed zone insertion bind: BIND: Denial of Service via crafted DNSSEC reply bind: BIND resolver: Denial of Service due to resource exhaustion in SVCB/HTTPS AliasMode processing bind: BIND 9: Remote Denial of Service via cached SVCB/HTTPS AliasMode records

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-19941 UBUNTU-CVE-2026-19941 2026-10-02T20:52:32.608394+00:00

Affected: Ubuntu:Pro:14.04:LTS: bind9, Ubuntu:Pro:16.04:LTS: bind9, Ubuntu:Pro:18.04:LTS: bind9, Ubuntu:18.04:LTS: isc-dhcp, Ubuntu:Pro:20.04:LTS: bind9, Ubuntu:20.04:LTS: bind9-libs, Ubuntu:22.04:LTS: bind9, Ubuntu:22.04:LTS: bind9-libs, Ubuntu:24.04:LTS: bind9, Ubuntu:24.04:LTS: isc-dhcp and 2 more

An inapplicable NSEC record may be accepted by a `named` resolver as proof that no wildcard exists, which could allow an attacker at the same or an upstream level of the zone name to mask the existence of a victim's wildcard record. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.

 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3420 WID-SEC-W-2026-3420 — Internet Systems Consortium BIND: Mehrere Schwachstellen 2026-10-02T20:52:32.608497+00:00

Ein entfernter Angreifer kann mehrere Schwachstellen in Internet Systems Consortium BIND ausnutzen, um Daten zu manipulieren, Sicherheitsmaßnahmen zu umgehen oder Denial-of-Service-Zustände herbeizuführen.