# CVE-2026-44932: indirect remote shell command injection via unsanitized DHCP options in wicked

> Attackers with a malicious DHCP server can execute arbitrary code on local machines using the wicked DHCP client due to unsanitized input.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Jun 2026
- **Updated:** 18 Jun 2026
- **Also known as:** GHSA-hc32-vf4h-9cg4, SUSE-SU-2026:2349-1, SUSE-SU-2026:2350-1, SUSE-SU-2026:2353-1, SUSE-SU-2026:2354-1, openSUSE-SU-2026:11018-1, openSUSE-SU-2026:20949-1

## What is CVE-2026-44932?

CVE-2026-44932 is a high-severity command injection vulnerability in SUSE wicked, published on 16 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-44932?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wicked` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 0.6.79-150400.3.39.1 |
| `wicked` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 0.6.79-150400.3.39.1 |
| `wicked` | SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 0.6.79-150500.3.42.1 |
| `wicked` | SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 0.6.79-150500.3.42.1 |
| `wicked` | SUSE:Linux Enterprise Micro 5.3 | All versions | 0.6.79-150400.3.39.1 |
| `wicked` | SUSE:Linux Enterprise Micro 5.4 | All versions | 0.6.79-150400.3.39.1 |
| `wicked` | SUSE:Linux Enterprise Micro 5.5 | All versions | 0.6.79-150500.3.42.1 |
| `wicked` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 0.6.79-150700.3.3.1 |
| `wicked` | SUSE:Linux Enterprise Server 12 SP5-LTSS | All versions | 0.6.79-3.56.1 |
| `wicked` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 0.6.79-150400.3.39.1 |
| `wicked` | SUSE:Linux Enterprise Server 15 SP5-LTSS | All versions | 0.6.79-150500.3.42.1 |
| `wicked` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 0.6.79-3.56.1 |
| `wicked` | SUSE:Linux Enterprise Server for SAP Applications 15 SP4 | All versions | 0.6.79-150400.3.39.1 |
| `wicked` | SUSE:Linux Enterprise Server for SAP Applications 15 SP5 | All versions | 0.6.79-150500.3.42.1 |
| `wicked` | openSUSE:Leap 16.0 | All versions | 0.6.79-bp160.1.1 |
| `wicked` | openSUSE:Tumbleweed | All versions | 0.6.79-1.1 |

## How do I fix CVE-2026-44932?

Upgrade to a fixed version.

## Is CVE-2026-44932 being exploited?

There is no known exploitation of CVE-2026-44932 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44932 and fix it if it is affected.

What it is: CVE-2026-44932 is a high-severity command injection vulnerability in SUSE wicked, published on 16 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-44932 in the wild and no public exploit code.

Affected product: SUSE wicked. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44932/ (Markdown: https://insights.sbomify.com/CVE-2026-44932/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44932
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44932
- OSV: https://osv.dev/vulnerability/CVE-2026-44932

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44932/
Summaries are generated and may contain mistakes; the official description above is the record.