dbcve.org
SolarisOperating system · Oracle

CVE-2026-46914

HIGH · 7.1 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
Zero-click

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: Filesystem). The supported version that is affected is 11.4. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where Oracle Solaris executes to compromise Oracle Solaris. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Solaris accessible data and unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle Solaris. CVSS 3.1 Base Score 7.1 (Confidentiality and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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 vulnerability in Oracle Solaris 11.4 filesystem component allows low-privileged authenticated users to gain unauthorized access to sensitive files and cause system crashes/DOS. Exploitable by any user with local login access.

MitigationApply Oracle Solaris 11.4 patchset when available; restrict local user privileges and monitor access to filesystem resources in the interim.

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.4

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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 installed Oracle Solaris version
    Affected if Version is Oracle Solaris 11.4 (the only affected version)
  2. Identify users with local login access
    Review /etc/passwd for local user accounts and check 'who' or 'last' commands to see who has active local sessions
    Affected if Multiple non-administrative user accounts exist with local login capability
  3. Audit sensitive file permissions
    Inspect permissions on critical system directories such as /etc, /var, and /root using 'ls -la' to identify files readable by non-privileged users
    Affected if Sensitive system files or configuration files are readable by regular (non-root) users
  4. Check for unauthorized file access patterns
    Review system audit logs and /var/adm/messages for repeated access attempts to restricted files by low-privileged users
    Affected if Logs show low-privileged users accessing files outside their normal scope
  5. Look for system instability or crashes
    Examine /var/adm/messages and crash dump directories for unexpected system crashes, panics, or DOS events
    Affected if Multiple filesystem-related crashes or system instabilities are logged

Environment is affected if running Oracle Solaris 11.4 with local non-administrative user accounts present, since the vulnerability allows those users to access sensitive files or cause system crashes.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Solaris 11.4 patchset when available; restrict local user privileges and monitor access to filesystem resources in the interim.

Recommended fix Moderate confidence
  1. Check Oracle's Critical Patch Update (CPU) advisories for the applicable quarter addressing CVE-2026-46914
  2. Navigate to Oracle Support (support.oracle.com) and search for CVE-2026-46914 or 'Oracle Solaris 11.4 Filesystem' security vulnerability
  3. Download and apply the specific Solaris patch identified in the security advisory
  4. Verify the patch was applied successfully using 'pkginfo -i <patch-id>' or 'patchadd -p'
  5. Reboot the Solaris system if required by the patch documentation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Solaris Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA2.0 h
19.0 hours of engineering $3,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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