Skip to content
statance
MenuClose
Log inStart for free ↗
high · CVSS 7.5

CVE-2026-6893

Dracut: dracut: root code execution via dhcp options command injection

Published 10 Jun 2026 · Source updated 2 Nov 2026 · Retrieved 2026-11-04 08:35 UTC · This record may be stale; verify the source

Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

A flaw was found in dracut. A remote attacker on the adjacent network can exploit this vulnerability by providing specially crafted DHCP (Dynamic Host Configuration Protocol) options, such as a malicious hostname, to a system using dracut's legacy DHCP path. These options are improperly handled and written into temporary shell scripts without proper escaping, leading to command injection. This allows the attacker to achieve root code execution within the initramfs, potentially compromising the system's boot and network behavior.

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
dracutRed Hatunaffected: 0:107-7.el10_2 to < *See vendor advisory
dracutRed Hatunaffected: 0:105-4.el10_0.1 to < *See vendor advisory
dracutRed Hatunaffected: 0:004-413.el6_10 to < *See vendor advisory
dracutRed Hatunaffected: 0:004-414.el6_10 to < *See vendor advisory
dracutRed Hatunaffected: 0:033-577.el7_9 to < *See vendor advisory
dracutRed Hatunaffected: 0:049-244.git20260529.el8_10 to < *See vendor advisory
dracutRed Hatunaffected: 0:049-138.git20220131.el8_4.1 to < *See vendor advisory
dracutRed Hatunaffected: 0:049-138.git20220131.el8_4.1 to < *See vendor advisory
dracutRed Hatunaffected: 0:049-203.git20220511.el8_6.1 to < *See vendor advisory
dracutRed Hatunaffected: 0:049-203.git20220511.el8_6.1 to < *See vendor advisory
dracutRed Hatunaffected: 0:049-223.git20230119.el8_8.1 to < *See vendor advisory
dracutRed Hatunaffected: 0:049-223.git20230119.el8_8.1 to < *See vendor advisory
dracutRed Hatunaffected: 0:057-115.git20260527.el9_8 to < *See vendor advisory
dracutRed Hatunaffected: 0:057-115.git20260527.el9_8 to < *See vendor advisory
dracutRed Hatunaffected: 0:057-25.git20250717.el9_2.2 to < *See vendor advisory
dracutRed Hatunaffected: 0:057-54.git20250423.el9_4.3 to < *See vendor advisory
dracutRed Hatunaffected: 0:057-89.git20250311.el9_6.1 to < *See vendor advisory
openshift/ose-rhel-coreos-8Red Hatunaffected: 412.86.202610250235-0 to < *See vendor advisory
openshift/ose-rhel-coreos-9Red Hatunaffected: 413.92.202609080414-0 to < *See vendor advisory
openshift/ose-rhel-coreos-9Red Hatunaffected: 414.92.202609011250-0 to < *See vendor advisory
openshift/ose-rhel-coreos-9Red Hatunaffected: 415.92.202609140326-0 to < *See vendor advisory
openshift/ose-rhel-coreos-9Red Hatunaffected: 416.94.202609011112-0 to < *See vendor advisory
openshift/ose-rhel-coreos-9Red Hatunaffected: 417.94.202609191027-0 to < *See vendor advisory
openshift/ose-rhel-coreos-9Red Hatunaffected: 418.94.202609031320-0 to < *See vendor advisory
openshift/ose-rhel-coreos-9Red Hatunaffected: 418.94.202609171815-0 to < *See vendor advisory
openshift/ose-rhel-coreos-9Red Hatunaffected: 4.19.9.6.202609021231-0 to < *See vendor advisory
dracut-mainRed Hatunaffected: 109-6.hum1 to < *See vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-06 16:38 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed