Technitium vulnerabilities
We track 9 vulnerabilities in Technitium products across 2 products. 9 are rated high or critical, and none are known to be exploited. The most recent was published on December 1, 2025.
Latest Technitium vulnerabilities
- 7.5 High severity
Dnsserver: Use of Insufficiently Random Values
An issue in Technitium through v13.2.2 enables attackers to conduct a DNS cache poisoning attack and inject fake responses by reviving the birthday attack.
- 7.5 High severity
dns_server: Insufficient Control of Network Message Volume (Network Amplification)
Technitium 11.5.3 allows remote attackers to cause a denial of service (bandwidth amplification) because the DNSBomb manipulation causes accumulation of low-rate DNS queries such that there is a large-sized response in a burst of traffic.
- 7.5 High severity
dns_server: Insufficient Verification of Data Authenticity
An issue was discovered in Technitium through 11.0.3. It enables attackers to conduct a DNS cache poisoning attack and inject fake responses within 1 second, which is impactful.
- 7.5 High severity
dns_server: Insufficient Control of Network Message Volume (Network Amplification)
An issue was discovered in Technitium through 11.0.2. It enables attackers to launch amplification attacks (3 times more than other "golden model" software like BIND) and cause potential DoS.
- 7.5 High severity
dns_server: Insufficient Control of Network Message Volume (Network Amplification)
An issue was discovered in Technitium through 11.0.2. The forwarding mode enables attackers to create a query loop using Technitium resolvers, launching amplification attacks and causing potential DoS.
- 7.5 High severity
dns_server: Uncontrolled Resource Consumption
An issue was discovered in Technitium 11.0.2. There is a vulnerability (called BadDNS) in DNS resolving software, which triggers a resolver to ignore valid responses, thus causing DoS (denial of service) for normal resolution. The effects of an exploit would b
- 7.5 High severity
dns_server: Uncontrolled Resource Consumption
The DNS protocol in RFC 1035 and updates allows remote attackers to cause a denial of service (resource consumption) by arranging for DNS queries to be accumulated for seconds, such that responses are later sent in a pulsing burst (which can be considered traf
- 9.8 Critical severity
DNS Server: Use of Incorrectly-Resolved Name or Reference
An issue was discovered in Technitium DNS Server through 8.0.2 that allows variant V2 of unintended domain name resolution. A revoked domain name can still be resolvable for a long time, including expired domains and taken-down malicious domains. The effects o
- 9.8 Critical severity
DNS Server: Use of Incorrectly-Resolved Name or Reference
An issue was discovered in Technitium DNS Server through 8.0.2 that allows variant V1 of unintended domain name resolution. A revoked domain name can still be resolvable for a long time, including expired domains and taken-down malicious domains. The effects o