Поиск уязвимостей
Количество 15
Количество 15
CVE-2026-46582
In NLnet Labs Unbound 1.6.0 up to and including 1.25.1, a replay of a wildcard rrset as another piece of data, could be briefly considered DNSSEC secure based only on the RRSIG validation and stored into cache, before later validation treats it as bogus based on NSEC validation. When the resolving thread puts secure on the rrset, and another thread that is on the serve expired path then picks up the updated rrset contents with the secure status for a reply, it can be used to change a specific record, next to a wildcard that could be covered by the wildcard, into the wildcard. A malicious actor can exploit the possible poisonous effect by having any DNSSEC-singed domain (irrelevant to the victim domain) and a CNAME wrapper record that points to a record next to a wildcard (that could be covered by the wildcard). Then quering Unbound for the wildcard sibling record would seed the secure message. A later (after expiry) query for the CNAME wrapper would need to resolve the target siblin...
CVE-2026-46582
In NLnet Labs Unbound 1.6.0 up to and including 1.25.1, a replay of a wildcard rrset as another piece of data, could be briefly considered DNSSEC secure based only on the RRSIG validation and stored into cache, before later validation treats it as bogus based on NSEC validation. When the resolving thread puts secure on the rrset, and another thread that is on the serve expired path then picks up the updated rrset contents with the secure status for a reply, it can be used to change a specific record, next to a wildcard that could be covered by the wildcard, into the wildcard. A malicious actor can exploit the possible poisonous effect by having any DNSSEC-singed domain (irrelevant to the victim domain) and a CNAME wrapper record that points to a record next to a wildcard (that could be covered by the wildcard). Then quering Unbound for the wildcard sibling record would seed the secure message. A later (after expiry) query for the CNAME wrapper would need to resolve the target siblin...
CVE-2026-46582
In NLnet Labs Unbound 1.6.0 up to and including 1.25.1, a replay of a wildcard rrset as another piece of data, could be briefly considered DNSSEC secure based only on the RRSIG validation and stored into cache, before later validation treats it as bogus based on NSEC validation. When the resolving thread puts secure on the rrset, and another thread that is on the serve expired path then picks up the updated rrset contents with the secure status for a reply, it can be used to change a specific record, next to a wildcard that could be covered by the wildcard, into the wildcard. A malicious actor can exploit the possible poisonous effect by having any DNSSEC-singed domain (irrelevant to the victim domain) and a CNAME wrapper record that points to a record next to a wildcard (that could be covered by the wildcard). Then quering Unbound for the wildcard sibling record would seed the secure message. A later (after expiry) query for the CNAME wrapper would need to resolve the target sibling r
CVE-2026-46582
A wildcard replay, as another piece of data, triggers poisoning in the serve expired reply path
CVE-2026-46582
In NLnet Labs Unbound 1.6.0 up to and including 1.25.1, a replay of a ...
ROS-20260921-80-0115
Уязвимость unbound
ROS-20260921-73-0092
Уязвимость unbound
GHSA-cj23-2crp-2xvv
In NLnet Labs Unbound 1.6.0 up to and including 1.25.1, a replay of a wildcard rrset as another piece of data, could be briefly considered DNSSEC secure based only on the RRSIG validation and stored into cache, before later validation treats it as bogus based on NSEC validation. When the resolving thread puts secure on the rrset, and another thread that is on the serve expired path then picks up the updated rrset contents with the secure status for a reply, it can be used to change a specific record, next to a wildcard that could be covered by the wildcard, into the wildcard. A malicious actor can exploit the possible poisonous effect by having any DNSSEC-singed domain (irrelevant to the victim domain) and a CNAME wrapper record that points to a record next to a wildcard (that could be covered by the wildcard). Then quering Unbound for the wildcard sibling record would seed the secure message. A later (after expiry) query for the CNAME wrapper would need to resolve the target siblin...
SUSE-SU-2026:3884-1
Security update for unbound
SUSE-SU-2026:3885-1
Security update for unbound
RLSA-2026:97497
Moderate: unbound security, bug fix, and enhancement update
RLSA-2026:97121
Moderate: unbound security, bug fix, and enhancement update
openSUSE-SU-2026:21550-1
Security update for unbound
ALT-PU-2026-11574
ALT-PU-2026-11574: package `unbound` update to version 1.25.2-alt1
ALT-PU-2026-11359
ALT-PU-2026-11359: package `unbound` update to version 1.25.2-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2026-46582 In NLnet Labs Unbound 1.6.0 up to and including 1.25.1, a replay of a wildcard rrset as another piece of data, could be briefly considered DNSSEC secure based only on the RRSIG validation and stored into cache, before later validation treats it as bogus based on NSEC validation. When the resolving thread puts secure on the rrset, and another thread that is on the serve expired path then picks up the updated rrset contents with the secure status for a reply, it can be used to change a specific record, next to a wildcard that could be covered by the wildcard, into the wildcard. A malicious actor can exploit the possible poisonous effect by having any DNSSEC-singed domain (irrelevant to the victim domain) and a CNAME wrapper record that points to a record next to a wildcard (that could be covered by the wildcard). Then quering Unbound for the wildcard sibling record would seed the secure message. A later (after expiry) query for the CNAME wrapper would need to resolve the target siblin... | CVSS3: 3.7 | 0% Низкий | 4 месяца назад | |
CVE-2026-46582 In NLnet Labs Unbound 1.6.0 up to and including 1.25.1, a replay of a wildcard rrset as another piece of data, could be briefly considered DNSSEC secure based only on the RRSIG validation and stored into cache, before later validation treats it as bogus based on NSEC validation. When the resolving thread puts secure on the rrset, and another thread that is on the serve expired path then picks up the updated rrset contents with the secure status for a reply, it can be used to change a specific record, next to a wildcard that could be covered by the wildcard, into the wildcard. A malicious actor can exploit the possible poisonous effect by having any DNSSEC-singed domain (irrelevant to the victim domain) and a CNAME wrapper record that points to a record next to a wildcard (that could be covered by the wildcard). Then quering Unbound for the wildcard sibling record would seed the secure message. A later (after expiry) query for the CNAME wrapper would need to resolve the target siblin... | CVSS3: 3.7 | 0% Низкий | 4 месяца назад | |
CVE-2026-46582 In NLnet Labs Unbound 1.6.0 up to and including 1.25.1, a replay of a wildcard rrset as another piece of data, could be briefly considered DNSSEC secure based only on the RRSIG validation and stored into cache, before later validation treats it as bogus based on NSEC validation. When the resolving thread puts secure on the rrset, and another thread that is on the serve expired path then picks up the updated rrset contents with the secure status for a reply, it can be used to change a specific record, next to a wildcard that could be covered by the wildcard, into the wildcard. A malicious actor can exploit the possible poisonous effect by having any DNSSEC-singed domain (irrelevant to the victim domain) and a CNAME wrapper record that points to a record next to a wildcard (that could be covered by the wildcard). Then quering Unbound for the wildcard sibling record would seed the secure message. A later (after expiry) query for the CNAME wrapper would need to resolve the target sibling r | CVSS3: 3.7 | 0% Низкий | 4 месяца назад | |
CVE-2026-46582 A wildcard replay, as another piece of data, triggers poisoning in the serve expired reply path | CVSS3: 3.7 | 0% Низкий | 4 месяца назад | |
CVE-2026-46582 In NLnet Labs Unbound 1.6.0 up to and including 1.25.1, a replay of a ... | CVSS3: 3.7 | 0% Низкий | 4 месяца назад | |
ROS-20260921-80-0115 Уязвимость unbound | CVSS3: 3.7 | 0% Низкий | около 2 месяцев назад | |
ROS-20260921-73-0092 Уязвимость unbound | CVSS3: 3.7 | 0% Низкий | около 2 месяцев назад | |
GHSA-cj23-2crp-2xvv In NLnet Labs Unbound 1.6.0 up to and including 1.25.1, a replay of a wildcard rrset as another piece of data, could be briefly considered DNSSEC secure based only on the RRSIG validation and stored into cache, before later validation treats it as bogus based on NSEC validation. When the resolving thread puts secure on the rrset, and another thread that is on the serve expired path then picks up the updated rrset contents with the secure status for a reply, it can be used to change a specific record, next to a wildcard that could be covered by the wildcard, into the wildcard. A malicious actor can exploit the possible poisonous effect by having any DNSSEC-singed domain (irrelevant to the victim domain) and a CNAME wrapper record that points to a record next to a wildcard (that could be covered by the wildcard). Then quering Unbound for the wildcard sibling record would seed the secure message. A later (after expiry) query for the CNAME wrapper would need to resolve the target siblin... | CVSS3: 3.7 | 0% Низкий | 4 месяца назад | |
SUSE-SU-2026:3884-1 Security update for unbound | 3 месяца назад | |||
SUSE-SU-2026:3885-1 Security update for unbound | 3 месяца назад | |||
RLSA-2026:97497 Moderate: unbound security, bug fix, and enhancement update | 5 дней назад | |||
RLSA-2026:97121 Moderate: unbound security, bug fix, and enhancement update | 5 дней назад | |||
openSUSE-SU-2026:21550-1 Security update for unbound | 3 месяца назад | |||
ALT-PU-2026-11574 ALT-PU-2026-11574: package `unbound` update to version 1.25.2-alt1 | CVSS3: 9.3 | 4 месяца назад | ||
ALT-PU-2026-11359 ALT-PU-2026-11359: package `unbound` update to version 1.25.2-alt1 | CVSS3: 9.3 | 4 месяца назад |
Уязвимостей на страницу