# CVE-2026-93008: Dnsmasq: dnsmasq: out-of-bailiwick cache injection through cname chase in split-dns configurations


- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-93008, GHSA-wpph-r7r5-526c

## What is CVE-2026-93008?

CVE-2026-93008 is a medium-severity vulnerability in Red Hat Ceph Storage 9, published on 29 Oct 2026. 

### Official description

A flaw was found in dnsmasq. When following a CNAME in a DNS response, the resolver can cache records for the CNAME target without checking that those records belong to the responding server's authorized zone. In split-DNS deployments that send some domains to a specific upstream, an attacker who controls that upstream can inject cache entries for unrelated names. Later clients may then receive attacker-chosen addresses for those names.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-93008?


## How do I fix CVE-2026-93008?

No fix has been published for CVE-2026-93008 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-93008 being exploited?

There is no known exploitation of CVE-2026-93008 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93008 and fix it if it is affected.

What it is: CVE-2026-93008 is a medium-severity vulnerability in Red Hat Ceph Storage 9, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-93008 in the wild and no public exploit code.

Affected product: Red Hat Ceph Storage 9. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93008/ (Markdown: https://insights.sbomify.com/CVE-2026-93008/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93008
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93008
- OSV: https://osv.dev/vulnerability/CVE-2026-93008

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93008/
Summaries are generated and may contain mistakes; the official description above is the record.