# CVE-2026-93011: Dnsmasq: dnsmasq: heap out-of-bounds write in dnssec validator via to_wire/from_wire transforms


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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-93011, GHSA-2jq5-wc7q-j2fc

## What is CVE-2026-93011?

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

### Official description

A flaw was found in dnsmasq. After a reduction of internal domain-name buffer sizes, the DNSSEC validator can write a few bytes past a name buffer when converting names to and from DNS wire format. An attacker who can cause the server to validate a crafted DNSSEC response may overwrite a small amount of adjacent heap metadata. DNSSEC support is not compiled in by default and must also be enabled at runtime.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

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

## Is CVE-2026-93011 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93011 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-93011 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-93011/ (Markdown: https://insights.sbomify.com/CVE-2026-93011/index.md)
```

## Sources

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

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