# CVE-2026-104114: NULL pointer dereference in illumos nwamd door handler allows local users to crash the daemon

> Local unprivileged users can crash the illumos nwamd daemon via a NULL pointer dereference, disrupting automatic network configuration.

- **Severity:** Medium 5.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Oct 2026
- **Updated:** 9 Oct 2026
- **Also known as:** GHSA-pc4c-24x9-97jq

## What is CVE-2026-104114?

CVE-2026-104114 is a medium-severity vulnerability in OmniOS, published on 9 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A NULL pointer dereference in the illumos Network Auto-Magic daemon (nwamd) allows a local user to crash the daemon. nwamd_door_switch() in usr/src/cmd/cmd-inet/lib/nwamd/door_if.c writes to the caller's request structure before checking that a request was supplied, and before checking the caller's credentials. Because the nwamd door at /etc/svc/volatile/nwam/nwam_door is accessible to all local users, an unprivileged user can issue a door_call() with no argument data to crash nwamd; repeated calls place the svc:/network/physical:nwam service into maintenance, stopping automatic network configuration. nwamd runs only when svc:/network/physical:nwam is enabled, which is not the default. The flaw has existed since 2010 (illumos-gate commit 6ba597c5), and affects any illumos distribution prior to illumos-gate commit 0f1064d9.

Weakness: CWE-476 (NULL Pointer Dereference)

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


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

No fix has been published for CVE-2026-104114 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-104114 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-104114 is a medium-severity vulnerability in OmniOS, published on 9 Oct 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-104114 in the wild and no public exploit code.

Affected product: OmniOS. 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-104114/ (Markdown: https://insights.sbomify.com/CVE-2026-104114/index.md)
```

## Sources

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

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