Skip to main content
Menu
CVEs

Red Hat denial of service in dnsmasq DHCPv6 relay

CVE-2026-133730Published , updated

5.9MediumCNA
Exploited
No known exploitation
Fix
See vendor advisory
Who is exposed
Not reported

Summary

Dnsmasq, the lightweight DNS and DHCP server, has a memory handling flaw in its DHCPv6 relay processing. A remote attacker without logging in can send a sequence of network packets to a system configured as a DHCPv6 relay, causing the service to crash and denying service to legitimate users.

Written by a model

Original description

A flaw was found in dnsmasq, where a memory handling issue exists in its Dynamic Host Configuration Protocol for IPv6 (DHCPv6) relay processing. A remote attacker can exploit this vulnerability by sending a sequence of network packets to a system configured as a DHCPv6 relay. This causes the service to write data to previously freed memory and crash, resulting in a Denial of Service (DoS).

What to do

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-133730 (Dnsmasq: dhcpv6 relay remote crash via stale pointer in relay_upstream6()), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133730 (entry last updated 2026-11-20):
Affected:
- Red Hat Red Hat Enterprise Linux 10: version range not reported
- Red Hat Red Hat Enterprise Linux 6: version range not reported
- Red Hat Red Hat Enterprise Linux 7: version range not reported
- Red Hat Red Hat Enterprise Linux 8: version range not reported
- Red Hat Red Hat Enterprise Linux 9: version range not reported
- Red Hat Red Hat OpenStack Platform 13 (Queens): version range not reported
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133730 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133730 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://bugzilla.redhat.com/show_bug.cgi?id=2578196
- https://access.redhat.com/security/cve/CVE-2026-133730
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133730
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133730"}.

Affected versions

cve.now Index

38Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach10/20Shipped in major Linux distributions
  • Severity5.9/10CVSS 5.9
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 83 if added to CISA KEV
  • Would score about 78 if CISA's SSVC rates exploitation active
  • Would score about 43 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 3

KindSource
CVE record 1Establishes: The identifier and description.
RecordCVE List · CVE-2026-133730
Write-ups 1Establishes: Technical detail and context.
Reportbugzilla.redhat.com · show_bug.cgi?id=2578196
Other links 1
Linkaccess.redhat.com · security/cve/CVE-2026-133730

No corrections so far. Something wrong on this page? Report an error.