How severe is GHSA-gv9j-4w24-q7vx?

No CVSS score has been assigned to GHSA-gv9j-4w24-q7vx yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-gv9j-4w24-q7vx?

GHSA-gv9j-4w24-q7vx affects the following packages: github.com/coredns/coredns (Go). Ecosystems affected: Go.

How do I fix GHSA-gv9j-4w24-q7vx?

Update github.com/coredns/coredns to 1.6.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gv9j-4w24-q7vx is resolved across your whole dependency graph.

How do I detect GHSA-gv9j-4w24-q7vx in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/coredns/coredns, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-gv9j-4w24-q7vx if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-gv9j-4w24-q7vx actively exploited in the wild?

No public exploit code has been indexed for GHSA-gv9j-4w24-q7vx yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-gv9j-4w24-q7vx published, and has it been updated?

GHSA-gv9j-4w24-q7vx was published on March 1, 2022 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

Improper random number generation in github.com/coredns/corednsGHSA-gv9j-4w24-q7vx

GHSA-gv9j-4w24-q7vx is a security vulnerability in github.com/coredns/coredns. A fix is available for github.com/coredns/coredns — see the affected versions and patch details below.

Also known asGO-2022-0368

Published

Mar 1, 2022

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 10, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐹github.com/coredns/coredns

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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.

Patches

The problem has been fixed in 1.6.6+.

References

CVE-2019-19794

For more information

Please consult our security guide for more information regarding our security process.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/coredns/coredns`	all versions	1.6.6`go get github.com/coredns/coredns@v1.6.6`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/coredns/coredns, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/coredns/coredns to 1.6.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gv9j-4w24-q7vx is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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. ### Patches The problem has been fixed in 1.6.6+. ### References - [CVE-2019-19794](https://nvd.nist.gov/vuln/detail/CVE-2019-19794) ### For more information Please consult [our security guide](https://github.com/coredns/coredns/blob/master/.github/SECURITY.md) for more information regarding our security process.

O3 Security · Impact-Aware SCA

Is GHSA-gv9j-4w24-q7vx in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works