published 22 Oct 2025 · updated 25 Nov 2025
Cache poisoning due to weak PRNG
8.6HighCVSS 8.6EPSS 0%
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.
In specific circumstances, due to a weakness in the Pseudo Random Number Generator (PRNG) that is used, it is possible for an attacker to predict the source port and query ID that BIND will use. This issue affects BIND 9 versions 9.16.0 through 9.16.50, 9.18.0 through 9.18.39, 9.20.0 through 9.20.13, 9.21.0 through 9.21.12, 9.16.8-S1 through 9.16.50-S1, 9.18.11-S1 through 9.18.39-S1, and 9.20.9-S1 through 9.20.13-S1.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| ISC | BIND | >=9.16.0 <=9.16.50, >=9.16.8-S1 <=9.16.50-S1, >=9.18.0 <=9.18.39, >=9.18.11-S1 <=9.18.39-S1, >=9.20.0 <=9.20.13, >=9.20.9-S1 <=9.20.13-S1, >=9.21.0 <=9.21.12 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in BIND, strongest first
10.0CriticalCISA KEVPublic exploit
Embed
A live severity badge for an advisory, README or ticket