CVE Intelligence
Medium Memory corruption

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

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.

Published Oct 29, 2026 · Updated Oct 30, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: redhat

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • Technical severity (medium)+3
  • Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
—
No EPSS score.
Affects
Red Hat
Red Hat Ceph Storage 9 and 9 more
CVSS base
5.3
Medium · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
Yes
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Red Hat Red Hat Ceph Storage 9, Red Hat Red Hat Enterprise Linux 10, Red Hat Red Hat Enterprise Linux 6…).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  4. Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Red Hat Red Hat Ceph Storage 9 versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
Red Hat Red Hat Enterprise Linux 10 versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
Red Hat Red Hat Enterprise Linux 6 versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
Red Hat Red Hat Enterprise Linux 7 versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
Red Hat Red Hat Enterprise Linux 8 versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
Red Hat Red Hat Enterprise Linux 9 versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
Red Hat Red Hat OpenShift Container Platform 4 versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
Red Hat Red Hat OpenShift Container Platform 5 versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
Red Hat Red Hat OpenStack Platform 13 (Queens) versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP
Red Hat Red Hat OpenStack Platform 18.0 versions not specified by the source Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
5.3 CVSS 3.1 Medium 3.9 1.4 secalert@redhat.com via NIST National Vulnerability Database
5.3 CVSS 3.1 Medium — — GitHub, Inc. via GitHub Security Advisories
5.3 CVSS 3.1 Medium — — redhat via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N (score shown at the top: secalert@redhat.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-787 · Out-of-bounds Write

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
web/proxy/WAF logsnetwork IDS/IPSendpoint telemetry (EDR)crash dumps

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · red hat/red hat openshift container platform 5
    Oct 30, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 29, 2026 · CVE Program (cve.org) e CISA ADP
  • Affected products added · red hat/red hat ceph storage 9, red hat/red hat enterprise linux 10, red hat/red hat enterprise linux 6, red hat/red hat
    Oct 29, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 29, 2026
  • CVSS changed · 5.3
    Oct 29, 2026 · NIST National Vulnerability Database
  • Source status changed · → Awaiting Analysis
    Oct 29, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 29, 2026 · Alertas do Telegram
  • CVE published
    Oct 29, 2026 · redhat

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 29, 2026 – Oct 30, 2026
  • 1× Official description updated · Oct 29, 2026 – Oct 29, 2026

References

4 on the record

Elsewhere on this site

Red Hat
every CVE for this vendor
CWE-787
other pages naming this weakness

Related CVEs (same products)

  • Medium CVE-2026-119842 Gst-plugins-base: gst-plugins-base: null-pointer dereference in mdvdsub subtitle parser via missing closing-brace check 2h
  • Medium CVE-2026-119729 Gst-plugins-base: gst-plugins-bad: gst-plugins-base/gst-plugins-bad: integer overflow in av1 leb128 parser allows denial of service 2h
  • Medium CVE-2026-119727 Gst-plugins-bad: gst-plugins-bad: h.265 sps scc palette predictor array overflow via integer underflow in bounds computation 2h
  • Medium CVE-2026-119728 Gst-plugins-bad: gst-plugins-bad: null pointer dereference in h.264 mvc sps cleanup during parse failure 2h
  • High CVE-2026-119777 Gstreamer1-plugins-bad-free: gstreamer1-plugins-bad-free: stack buffer overflow in h.266/vvc parser 3h
  • High CVE-2026-119528 Gimp: gimp: stack buffer overflow in psd image resource header loader 7h

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No FIRST EPSS score.
  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-93011 is "Dnsmasq: dnsmasq: heap out-of-bounds write in dnssec validator via to_wire/from_wire transforms", rated Medium. It affects Red Hat Ceph Storage 9 (Red Hat); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.3 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.