Critical Security Update for BIND 9.16: Cache Poisoning Vulnerabilities

bind9.16 Updated 10 Nov 2025

Summary

05/11/2025
N/A
Yes i
Unrated
Not published

ALSA-2025:19793: Important: bind9.16 security update. Affects bind9.16 versions < 32:9.16.23-0.22.el8_10.4. Fixed in 32:9.16.23-0.22.el8_10.4. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

BIND (Berkeley Internet Name Domain) is a widely used implementation of the Domain Name System (DNS) protocols. It includes a DNS server (named), a resolver library, and various tools for DNS management. BIND is essential for translating human-readable domain names into IP addresses, making it a cornerstone of internet functionality. However, recent vulnerabilities have been identified that could compromise its integrity and security.

Vulnerability Detail

The vulnerabilities identified in BIND 9.16 include cache poisoning attacks due to unsolicited Resource Records (RRs) and weaknesses in the Pseudo-Random Number Generator (PRNG). These issues can allow attackers to manipulate DNS responses, potentially redirecting users to malicious sites or intercepting sensitive data. The vulnerabilities are tracked under CVE-2025-40778 and CVE-2025-40780, respectively.

How To Fix

Minimum fixed version

32:9.16.23-0.22.el8_10.4

This is the first release that contains the fix.

sudo dnf update bind9.16

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary measure, users can limit the exposure of their DNS servers by implementing access controls and filtering incoming requests to mitigate the risk of cache poisoning attacks. However, this is not a substitute for applying the security update.

Conclusion

The recent vulnerabilities in BIND 9.16 pose significant risks to DNS security. It is essential for users to update to the latest patched version to protect against cache poisoning attacks. Utilizing tools like Vulert can help monitor for vulnerabilities and ensure ongoing security.

See every vulnerability recorded for bind9.16 →

Share this vulnerability

FAQ

Cache poisoning is a type of attack where an attacker inserts false information into a DNS cache, causing users to be directed to malicious sites.

You can check if your application is affected by using the Vulert playground at Vulert Scanner, which analyzes your manifest file for vulnerabilities.

Failing to update BIND can leave your DNS server vulnerable to attacks, potentially leading to data breaches and loss of user trust.

Yes, Vulert provides a service that monitors and alerts for open-source vulnerabilities in your software without requiring code access.

If immediate updates are not possible, implement strict access controls and monitor DNS traffic for unusual activity as a temporary workaround.

Related vulnerabilities

Recent vulnerabilities recorded for bind9.16.

How To Fix

Minimum fixed version

32:9.16.23-0.22.el8_10.4

This is the first release that contains the fix.

sudo dnf update bind9.16

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback