Skip to content
VulniPulse
High8.8Red Hat Linux

High [CVE-2026-44932] Arbitrary code execution via unsanitized DHCP replies

This high-severity Red Hat Linux advisory covers CVE-2026-44932.

CVE-2026-44932 Published Jun 16, 2026Updated by vendor Jun 16, 2026
Affected products & platforms
Red Hat LinuxUnclassified
Open vendor advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

Passing of unsanitized strings from DHCP replies into the wicked dhcp client before wicked 0.6.79 could be used by attackers operating a malicious DHCP server to execute code on the local machine.

A remote attacker, by operating a malicious Dynamic Host Configuration Protocol (DHCP) server, could send specially crafted DHCP replies containing unsanitized strings. This vulnerability allows the attacker to execute arbitrary code on the local machine, potentially leading to a complete compromise of the affected system.

This Important vulnerability in the wicked DHCP client allows a remote attacker to achieve arbitrary code execution on a system configured to obtain an IP address from a malicious DHCP server. By sending specially crafted DHCP replies, an attacker can exploit unsanitized strings, leading to a complete compromise of the affected system.

This risk is primarily present in environments where systems are exposed to untrusted DHCP servers. Red Hat severity: Important — CVSS 8.8 (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Weakness: CWE-94.

Affected versions
  • < 0.6.79

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • To mitigate this issue, configure systems with static IP addresses instead of relying on DHCP, especially when operating on untrusted network segments. Alternatively, ensure that DHCP services are only obtained from trusted and controlled network environments. If a service is restarted or the network configuration is reloaded, these changes will take effect.

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.