dbcve.org
SolarisOperating system · Oracle

CVE-2026-21942

MEDIUM · 5.0 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 →
50/100
Remediation priority · Moderate

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: Filesystems). Supported versions that are affected are 10 and 11. Easily exploitable vulnerability allows low 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 ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle Solaris. CVSS 3.1 Base Score 5.0 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H).

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

Local privilege escalation/denial of service vulnerability in the Filesystems component of Oracle Solaris 10 and 11. Allows a low-privileged attacker with local system access to cause a system hang or repeatable crash, though exploitation requires human interaction from another person.

MitigationRestrict local user privileges and access to Solaris systems; monitor for suspicious filesystem activity; apply Oracle Solaris patches when released; consider isolating affected systems until patch is available.

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:= 10= 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
Low
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

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 version
    Run 'uname -a' or 'cat /etc/release' to identify the exact Oracle Solaris version (10 or 11.x)
    Affected if The version is Oracle Solaris 10 or Oracle Solaris 11 (any update) without Oracle patches applied
  2. Verify local user access exists
    Check for the presence of local user accounts using 'getent passwd' or 'logins' command; review /etc/passwd for non-privileged accounts
    Affected if Low-privileged local user accounts exist on the system and can log in locally
  3. Check Filesystem component status
    Review mounted filesystems with 'mount -v' or 'df -k'; check for any custom or third-party filesystem configurations
    Affected if Non-standard filesystems are mounted or filesystem services are running beyond default configurations
  4. Assess user privileges
    Run 'roles' or 'pr privileges' for test user accounts to determine if low-privilege users have filesystem-related privileges
    Affected if Low-privileged users have elevated filesystem privileges or can access administrative filesystem operations
  5. Review system access controls
    Check /etc/login.conf or PAM configuration for local access restrictions; examine 'who -r' for run-level settings
    Affected if Local console or terminal access is available to untrusted users without additional verification

The environment is affected if running Oracle Solaris 10 or 11 with low-privileged local user accounts who can access the system locally and interact with filesystems, as the vulnerability requires local access and human interaction to trigger the denial of service.

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

Restrict local user privileges and access to Solaris systems; monitor for suspicious filesystem activity; apply Oracle Solaris patches when released; consider isolating affected systems until patch is available.

Fix this in Solaris Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-21942 — 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-21942 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