Actively exploited

CVE-2020-14871 Oracle Solaris and Zettabyte File System (ZFS) Unspecified Vulnerability

Oracle Solaris and Oracle ZFS Storage Appliance Kit contain an unspecified vulnerability causing high impacts to confidentiality, integrity, and availability of affected systems.

From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.

Our Assessment

Should You Worry?

Patch nowCybergen assessment
  • CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 3 Nov 2021.
  • Rated Critical severity (CVSS 10.0, scored by Vendor).
  • It has been in the catalogue for 1,829 days. Systems still unpatched now have almost certainly been scanned for it.
The Vulnerability

What It Is

Vulnerability in the Oracle Solaris product of Oracle Systems (component: Pluggable authentication module). Supported versions that are affected are 10 and 11. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Solaris. While the vulnerability is in Oracle Solaris, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of Oracle Solaris. Note: This CVE is not exploitable for Solaris 11.1 and later releases, and ZFSSA 8.7 and later releases, thus the CVSS Base Score is 0.0. CVSS 3.1 Base Score 10.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H).

Affected Versions

ProductVersions
Oracle Corporation Solaris Operating System10
11

From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.

From Watch to Action

What To Do Now

  1. 1

    Find it

    Search your asset inventory and external attack surface for Oracle Solaris and Zettabyte File System (ZFS). Include cloud images, appliances and anything a supplier runs for you.

    Attack Surface Management
  2. 2

    Fix it

    Apply updates per vendor instructions.

    Vulnerability Management
  3. 3

    Hunt for compromise

    If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.

    Incident Response
  4. 4

    Prove it is fixed

    Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.

    Penetration Testing

Not Sure If You Are Exposed?

Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2020-14871 and every other exploited flaw on the list.

Check My Exposure