# CVE-2026-21927: Missing authorization in Oracle Solaris

> High-privileged attackers can modify or read critical data in Oracle Solaris via a driver vulnerability requiring user interaction.

- **Severity:** Medium 5.8 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Jan 2026
- **Updated:** 3 Mar 2026
- **Also known as:** GHSA-f4hj-p58g-9m5p

## What is CVE-2026-21927?

CVE-2026-21927 is a medium-severity missing authorization vulnerability in Oracle Solaris, published on 20 Jan 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Vulnerability in the Oracle Solaris product of Oracle Systems (component: Driver).   The supported version that is affected is 11. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle Solaris executes to compromise Oracle Solaris.  Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in  unauthorized creation, deletion or modification access to critical data or all Oracle Solaris accessible data as well as  unauthorized access to critical data or complete access to all Oracle Solaris accessible data. CVSS 3.1 Base Score 5.8 (Confidentiality and Integrity impacts).  CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:N).

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

It affects 1 product.


Products: Oracle Solaris.

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

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

## Is CVE-2026-21927 being exploited?

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

## Other vulnerabilities in Oracle Solaris

- [CVE-2020-14871](https://insights.sbomify.com/CVE-2020-14871/): Oracle Solaris and Zettabyte File System (ZFS) Unspecified (critical 10.0, exploited in the wild)
- [CVE-2019-3010](https://insights.sbomify.com/CVE-2019-3010/): Oracle Solaris Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2026-46978](https://insights.sbomify.com/CVE-2026-46978/): Missing authorization in Oracle Solaris (critical 10.0)
- [CVE-2017-3623](https://insights.sbomify.com/CVE-2017-3623/): Other in Solaris Operating System (critical 10.0)
- [CVE-2014-0397](https://insights.sbomify.com/CVE-2014-0397/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-21927 is a medium-severity missing authorization vulnerability in Oracle Solaris, published on 20 Jan 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-21927 in the wild and no public exploit code.

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

## Sources

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

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