CoreDNS vulnerable to TuDoor Attacks

Answer in brief

CVE-2023-28452 records a Medium severity (CVSS 5.9) vulnerability in CoreDNS vulnerable to TuDoor Attacks. The current sources do not mark it as known exploited. The current feed maps github.com/coredns/coredns (go). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 18, 2024Updated Sep 10, 2026Source checked Sep 10, 2026First seen by HOL Aug 7, 2026Material review Sep 10, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 5.9
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 5.9. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps github.com/coredns/coredns (go). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
github.com/coredns/corednsgo	>=0 <1.11.0	1.11.0

Recommended response

Check inventory. Check lockfiles and deployed manifests for github.com/coredns/coredns.
Review the reported fix. Update github.com/coredns/coredns to 1.11.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 18, 2024
Evidence: source:osv:source_dates:source-dates:record
Source modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:record
First seen by HOL
Aug 7, 2026

Sources and claim methodology

Upstream source description

An issue was discovered in CoreDNS through 1.10.1. There is a vulnerability in DNS resolving software, which triggers a resolver to ignore valid responses, thus causing denial of service for normal resolution. In an exploit, the attacker could just forge a response targeting the source port of a vulnerable resolver without the need to guess the correct TXID.

Quoted source text, attributed separately from HOL analysis.