# CVE-2026-104117: Missing authorization in illumos ipmgmtd allows local users to change persistent IPMP group membership

> Local users can modify persistent IPMP group configurations due to missing authorization checks, potentially disrupting network connectivity at boot.

- **Severity:** Low 1.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/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-m2wm-6wgg-68w9

## What is CVE-2026-104117?

CVE-2026-104117 is a low-severity missing authorization 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 missing authorization check in the illumos IP management daemon (ipmgmtd) allows a local user to change the persistent IP multipathing (IPMP) configuration. The ipmgmtd door dispatch table in usr/src/cmd/cmd-inet/lib/ipmgmtd/ipmgmt_door.c does not require the solaris.network.interface.config authorization for the IPMGMT_CMD_IPMP_UPDATE command, although its handler, ipmgmt_ipmp_update_handler(), writes to the persistent ipadm configuration when the IPMGMT_PERSIST flag is set. An unprivileged local user can therefore add interfaces to, or remove them from, existing IPMP groups in the stored configuration. The running configuration is not changed; the modification takes effect when the stored configuration is next applied, such as at boot, and may disrupt network connectivity. The flaw has existed since 2021 (illumos-gate commit a73be61a), and affects any illumos distribution prior to illumos-gate commit e8d3efa1.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-104117 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-104117 is a low-severity missing authorization 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-104117 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-104117/ (Markdown: https://insights.sbomify.com/CVE-2026-104117/index.md)
```

## Sources

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

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