{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-62309 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-62309 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-62309 is a high-severity vulnerability in coredns, published on 16 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-62309 and fix it if it is affected.\n\nWhat it is: CVE-2026-62309 is a high-severity vulnerability in coredns, published on 16 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-62309 in the wild and no public exploit code.\n\nAffected product: coredns. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-62309/ (Markdown: https://insights.sbomify.com/CVE-2026-62309/index.md)","id":"CVE-2026-62309","markdown":"https://insights.sbomify.com/CVE-2026-62309/index.md","name":"CVE-2026-62309","record":{"aliases":["GHSA-9rvv-m5g5-wc8r"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"CoreDNS server","requires_auth":"none","summary":"Remote attackers can crash CoreDNS via a single UDP packet if the proxyproto plugin is enabled, causing denial of service.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"coredns","vendor":"coredns.io"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"CoreDNS is a DNS server written in Go. Prior to 1.14.4, a single 28-byte UDP datagram can crash the CoreDNS process when the proxyproto plugin is enabled because plugin/pkg/proxyproto/proxyproto.go PacketConn.ReadFrom handles a PROXY v2 header with non-UDP transport such as family byte 0x11, reassigns addr from a nil readFrom result after parseProxyProtocol errors, and calls addr.String() in the warning log before ServeDNS recovery applies. This issue is fixed in version 1.14.4.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"CoreDNS: proxyproto plugin panics on PPv2 datagram with non-UDP transport — single 28-byte packet remote DoS","id":"CVE-2026-62309","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"9Router: Authenticated RCE via Unvalidated MCP Plugin Arguments","id":"CVE-2026-62312"},"packages":[],"prev":{"headline":"Tugtainer: Authenticated SSRF via arbitrary notification URLs in test_notification endpoint","id":"CVE-2026-62308"},"products":["coredns"],"published":"2026-07-16","related":[{"cvss_score":8.7,"headline":"CoreDNS DNS-over-QUIC unbounded goroutine growth leads to denial of service","id":"CVE-2026-32934","kev_date_added":null,"published":"2026-05-05"},{"cvss_score":8.7,"headline":"CoreDNS DoH GET path missing size validation causes CPU and memory amplification","id":"CVE-2026-32936","kev_date_added":null,"published":"2026-05-05"},{"cvss_score":8.7,"headline":"CoreDNS TSIG authentication bypass on encrypted DNS transports","id":"CVE-2026-33190","kev_date_added":null,"published":"2026-05-05"},{"cvss_score":8.2,"headline":"CoreDNS transfer plugin subzone ACL bypass via lexicographic zone comparison","id":"CVE-2026-33489","kev_date_added":null,"published":"2026-05-05"},{"cvss_score":8.2,"headline":"CoreDNS TSIG authentication bypass on gRPC, QUIC, DoH, and DoH3 transports","id":"CVE-2026-35579","kev_date_added":null,"published":"2026-05-05"},{"cvss_score":7.7,"headline":"CoreDNS ACL Bypass","id":"CVE-2026-26017","kev_date_added":null,"published":"2026-03-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-18","vendors":["coredns"]},"summary":"Remote attackers can crash CoreDNS via a single UDP packet if the proxyproto plugin is enabled, causing denial of service.","url":"https://insights.sbomify.com/CVE-2026-62309/"}