CVE-2026-93008Network attack vector

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.

CVSS severity6.8
Medium
EPSS probability0.15%
Next 30 days · Nov 22, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Contact us

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

  1. Oct 29, 2026CVE publishedPublication date reported by the CVE source.
  2. 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?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

John Horne · Red Hat OpenShift Container PlatformAffected versions are unavailable in this record.
John Horne · Red Hat Enterprise Linux 10Affected versions are unavailable in this record.
John Horne · Red Hat Enterprise Linux 9Affected versions are unavailable in this record.
John Horne · Red Hat Enterprise Linux 8Affected versions are unavailable in this record.
John Horne · Red Hat Enterprise LinuxAffected versions are unavailable in this record.
John Horne · Red Hat OpenStack PlatformAffected versions are unavailable in this record.
John Horne · Red Hat Ceph StorageAffected versions are unavailable in this record.

Published CVSS scores

6.8Red HatCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-345Insufficient Verification of Data Authenticity
T1557Adversary-in-the-Middle

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