Skip to content
VulniPulse
Low 2 vendors · 2 advisories

CVE-2026-106587: OpenSSH Vulnerability in NetApp Products

CVE-2026-106587 key facts

CISA KEV
Not listed (catalogue checked )
Highest advisory rating
Low
CVSS base score
3.6 (NetApp), 3.6 (Red Hat)
CVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L · base score 3.6, scored by mitreAttack vector: local. Attack complexity: high. Privileges required: low. User interaction: none. Scope: unchanged. Confidentiality impact: none. Integrity impact: low. Availability impact: low.
Weakness
  • CWE-843 Access of Resource Using Incompatible Type ('Type Confusion')
EPSS
0.08% chance of exploitation in the next 30 days (0th percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: no. Technical impact: partial. CISA, .
Fixed releases
  • Red Hat: openssh-main-10.5p1-1.2.hum1, RHSA-2026:82247
Vendor advisories
2 from NetApp, Red Hat
Assigned by
mitre (CNA)
CVE record published
Listed by VulniPulse
Record changed

Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-106587; each belongs to its advisory, not to every product listed. How records are collected and checked.

Description

In sshd in OpenSSH before 10.6, the value "none" for a configuration option is sometimes interpreted as a filename but was intended to mean that a feature is disabled.

Text from the CVE.org record (mitre).

How do I fix CVE-2026-106587?

Upgrade to a fixed release named by the vendor:

  • Red Hat: openssh-main-10.5p1-1.2.hum1, RHSA-2026:82247
  • As a workaround, avoid setting options that accept the value "none" (for example AuthorizedPrincipalsFile) inside sshd_config Match blocks, where sshd misinterprets the value as a literal file path. Instead, apply the "none" value at the global configuration level outside of Match blocks, where it correctly disables the feature, or restructure the configuration so that these options are not set to "none" via a Match keyword. This prevents sshd from reading a file named "none" that may be controlled by a local user. Alternatively, updating to a version of OpenSSH that includes the upstream fix resolves the issue. (Red Hat)

Vendor advisories for CVE-2026-106587

NetApp

1 advisory
  • Advisory severityLow3.6

    Low [CVE-2026-106587] OpenSSH Vulnerability in NetApp Products

    NTAP-20261118-0016Source published Source updated

    OpenSSH versions through 10.5-p1 are susceptible to a vulnerability which when successfully exploited could allow an attacker to interfere with expected security controls. Successful exploitation of this vulnerability could lead to addition or modification of data or Denial of Service (DoS). NetApp reports that one or more additional products remain under investigation; review the canonical advisory for current status. NetApp states there is no workaround available at this time.

    Affected products in this advisory
    No product details extracted. Check the source bulletin.
    Source-reported affected versions
    • 10.5-p1
    Source-reported fixed versions
    No fixed-version detail extracted. This does not mean no fix exists.
    Mitigation guidance
    No mitigation guidance extracted; consult the source.

Red Hat

1 advisory
  • Advisory severityLow3.6

    Low [CVE-2026-106587] Improper access control via misinterpretation of disabled configuration options

    CVE-2026-106587Source published Source updated

    Improper access control via misinterpretation of disabled configuration options. Red Hat rates this low (CVSS 3.6). Weakness: CWE-115. Red Hat lists fixing advisory RHSA-2026:82247 with package openssh-main-10.5p1-1.2.hum1. Affected product named by the advisory: Red Hat Hardened Images.

    Related products — impact not confirmed
    • Red Hat Hardened Images
    Source-reported affected versions
    • < 10.6
    Source-reported fixed versions
    • openssh-main-10.5p1-1.2.hum1
    • RHSA-2026:82247
    Mitigation guidance
    • As a workaround, avoid setting options that accept the value "none" (for example AuthorizedPrincipalsFile) inside sshd_config Match blocks, where sshd misinterprets the value as a literal file path. Instead, apply the "none" value at the global configuration level outside of Match blocks, where it correctly disables the feature, or restructure the configuration so that these options are not set to "none" via a Match keyword. This prevents sshd from reading a file named "none" that may be controlled by a local user. Alternatively, updating to a version of OpenSSH that includes the upstream fix resolves the issue.

References

Timeline

  1. CVE record published
  2. CVE record last updated
  3. First vendor advisory listed by VulniPulse

All NetApp advisories

Get an email when NetApp publishes the next one.

See NetApp's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about NetApp