dbcve.org
SolarisOperating system · Oracle

CVE-2026-21935

MEDIUM · 5.8 CVSS v3.1 Published 2026-01-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A vulnerability in the Driver component of Oracle Solaris 11 allows a high-privileged attacker with local system access to compromise the system through human interaction. Successful exploitation enables unauthorized creation, deletion, or modification of critical data, as well as unauthorized access to critical or all Oracle Solaris accessible data, with high confidentiality and integrity impacts.

MitigationApply Oracle's security patch for this Driver vulnerability in Solaris 11 when available. Restrict local system access to trusted, high-privileged administrators only, and monitor for suspicious local activity that could indicate exploitation attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SolarisOperating system
Affected:= 11

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
High
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Oracle Solaris 11 is installed
    Run `uname -a` or `cat /etc/release` to identify the operating system and exact version number
    Affected if The system is running Oracle Solaris version 11 (exact match)
  2. Identify loaded kernel driver modules
    Run `modinfo -c` to list all loaded kernel modules and their status, or use `ls -la /kernel/drv/` to view available driver files
    Affected if Any driver module is loaded that corresponds to the vulnerable Driver component for this CVE
  3. Check for unknown or unauthorized driver modules
    Compare the list of loaded drivers against your documented baseline of expected drivers for this Solaris 11 system
    Affected if Unexpected or undocumented driver modules are present that could be related to this Driver vulnerability
  4. Review driver configuration files
    Examine configuration files in `/etc/driver_aliases` and `/kernel/drv/*.conf` for any unexpected driver bindings or modifications
    Affected if Driver configuration has been altered from the baseline or contains suspicious entries

A user is affected if the system runs Oracle Solaris 11 and has the vulnerable Driver component loaded or configured, particularly if untrusted high-privileged access is possible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle's security patch for this Driver vulnerability in Solaris 11 when available. Restrict local system access to trusted, high-privileged administrators only, and monitor for suspicious local activity that could indicate exploitation attempts.

Fix this in Solaris Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing10.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,776.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-21935 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-21935 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data