# CVE-2026-104116: Missing authorization in illumos zonestatd allows local users to disrupt zonestat and enumerate running zones

> Local users can disrupt zone statistics and enumerate running zones due to missing authorization checks in the illumos zonestatd daemon.

- **Severity:** Low 1.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/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-83mv-pfw5-3x3p

## What is CVE-2026-104116?

CVE-2026-104116 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 zones statistics daemon (zonestatd) allows a local user in any zone to disrupt zonestat in other zones and to determine which zones are running. The zonestatd door server procedure, zsd_server() in usr/src/cmd/zonestat/zonestatd/zonestatd.c, handles the ZSD_CMD_NEW_ZONE command, which is intended to be sent by zoneadmd, without checking the caller's credentials. Because the zonestatd door is accessible to all users in every zone, an unprivileged user can send this command with an arbitrary zone ID, causing zonestatd to re-create its door file in that zone, so that new zonestat requests in that zone can fail while the file is replaced. The time taken to handle the command also reveals whether a given zone ID belongs to a running zone. The flaw has existed since 2010 (illumos-gate commit efd4c9b6), and affects any illumos distribution prior to illumos-gate commit 865b58d2.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-104116 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-104116 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-104116 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-104116/ (Markdown: https://insights.sbomify.com/CVE-2026-104116/index.md)
```

## Sources

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

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