Summary
Improper random number generation in github.com/coredns/coredns
References
For more information
Please consult our security guide for more information regarding our security process.
Impact
CoreDNS before 1.6.6 (using go DNS package < 1.1.25) improperly generates random numbers because math/rand is used. The TXID becomes predictable, leading to response forgeries.
Security-sensitive operations rely on values that are predictable or insufficiently random. Typical impact: forged tokens, guessable identifiers, or broken cryptographic protocols.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
The problem has been fixed in 1.6.6+.
Frequently Asked Questions
- What is GHSA-GV9J-4W24-Q7VX? GHSA-GV9J-4W24-Q7VX is a medium-severity use of insufficiently random values vulnerability in github.com/coredns/coredns (go), affecting versions < 1.6.6. It is fixed in 1.6.6. Security-sensitive operations rely on values that are predictable or insufficiently random.
- Which versions of github.com/coredns/coredns are affected by GHSA-GV9J-4W24-Q7VX? github.com/coredns/coredns (go) versions < 1.6.6 is affected.
- Is there a fix for GHSA-GV9J-4W24-Q7VX? Yes. GHSA-GV9J-4W24-Q7VX is fixed in 1.6.6. Upgrade to this version or later.
- Is GHSA-GV9J-4W24-Q7VX exploitable, and should I be worried? Whether GHSA-GV9J-4W24-Q7VX is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-GV9J-4W24-Q7VX is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-GV9J-4W24-Q7VX? Upgrade
github.com/coredns/corednsto 1.6.6 or later.