LiveActive security incident?Get immediate response
CVE Record

CVE-2026-2291: CVE-2026-2291

dnsmasqs extract_name() function can be abused to cause a heap buffer overflow, allowing an attacker to inject false DNS cache entries, which could result in DNS lookups to redirect to an attacker-controlled IP address, or to cause a DoS.

HighCVSS 7.3Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-2291 is a dnsmasq DNS handling flaw that can corrupt memory and potentially poison DNS cache responses. A successful attacker could redirect users to attacker-controlled IP addresses or disrupt DNS service. The provided data rates it high severity, but does not show confirmed active exploitation.

Executive priority

Prioritize remediation for internet-facing or broadly reachable DNS infrastructure because DNS redirection can undermine trust in many dependent services. Internal-only deployments still matter, but urgency should follow reachability and package-maintainer confirmation.

Technical view

The issue is described as a heap buffer overflow in dnsmasq extract_name(), associated with CWE-190. The CVSS 3.1 score is 7.3 with network attack vector, low complexity, no privileges, and no user interaction. Impact is limited but spans confidentiality, integrity, and availability.

Likely exposure

Exposure is likely where dnsmasq is reachable as a DNS resolver, forwarder, or cache, especially if queries can arrive from untrusted networks. Version data in the bundle is incomplete, so asset teams should verify against vendor and package-maintainer advisories.

Exploitation context

The bundle says exploitation could inject false DNS cache entries or cause denial of service. It does not provide evidence of exploitation in the wild, and the KEV flag is false. Treat exploitability as plausible from network access, but not confirmed as actively exploited.

Researcher notes

The source bundle identifies dnsmasq and extract_name(), but affected version ranges are not well specified. Downstream references suggest package ecosystems are responding, yet the bundle does not prove which downstream products are affected. Avoid claims beyond dnsmasq until advisories confirm scope.

Mitigation direction

  • Check dnsmasq project and OS vendor advisories for fixed versions.
  • Update dnsmasq or downstream packages once vendor-fixed builds are available.
  • Restrict DNS service access to trusted clients and networks.
  • Review firewall rules for unintended public DNS exposure.
  • Monitor resolver behavior for suspicious cache or redirect anomalies.

Validation and detection

  • Inventory systems running dnsmasq or bundled dnsmasq derivatives.
  • Compare installed package versions against vendor advisory status.
  • Confirm DNS listeners are not exposed beyond intended networks.
  • Review resolver logs for crashes, abnormal responses, or cache anomalies.
  • Track SUSE, CERT/CC, dnsmasq, NixOS, and Pi-hole references for updates.
Prepared
Confidence
medium
Sources
9

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-190: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-2291 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
2ADP providers
8Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.3CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L3.93.4CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.3High
CVSS 3.1 vector shape for CVE-2026-2291Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
dnsmasqdnsmasq0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-190 · source CWE mapping

Integer Overflow or Wraparound

Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.