Cache poisoning via unchecked CNAME target records
Published Oct 29, 2026 · Updated Oct 29, 2026
Cache poisoning in dnsmasq's DNS resolver allows remote attackers to redirect clients through crafted upstream CNAME responses. In src/rfc1035.c, cname_loop replaces the tracked query name with the CNAME target and caches matching answer records without validating the responding server's zone authority. Exploitation requires control of an upstream across a split-DNS or local-domain trust boundary; subsequent clients receive attacker-chosen addresses for unrelated names.
Summary
What happened
Cache poisoning in dnsmasq's DNS resolver allows remote attackers to redirect clients through crafted upstream CNAME responses. In src/rfc1035.c, cname_loop replaces the tracked query name with the CNAME target and caches matching answer records without validating the responding server's zone authority. Exploitation requires control of an upstream across a split-DNS or local-domain trust boundary; subsequent clients receive attacker-chosen addresses for unrelated names.
The record
- CVE
- CVE-2026-93008
- Published
- Oct 29, 2026
- Updated
- Oct 29, 2026
- Vendor
- John Horne
- Product
- Red Hat OpenShift Container Platform
- Classifications
- CWE-345, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 29, 2026CVE publishedPublication date reported by the CVE source.
- Oct 29, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us