There are packages installed that are affected by multiple vulnerabilities referenced in the following CVEs:

  - A certificate with no dNSName SAN but another SAN type present (e.g. registeredID or iPAddress) bypassed
    the Subject CN dNSName name-constraint check. The CN-as-DNS fallback was gated on cert->subjectCN != NULL
    && cert->altNames == NULL && !cert->isCA instead of "no dNSName SAN", so an out-of-scope CN was accepted.
    This incomplete fix from CVE-2026-6731, leading to the name-constraint check issue, was introduced in
    wolfSSL version 5.9.2. (CVE-2026-89134)

  - In all builds that make use of (D)TLS, including default builds, there is a series of conditional states
    during the TLS shutdown which could lead to a heap-use-after free. If an application ended up getting a
    partial wolfSSL_read() which is sometimes caused by a small user buffer passed in, then called
    wolfSSL_shutdown for a bidirectional close and attempted to wolfSSL_read() again while the peer continues
    trying to send data during the shutdown it would lead to a state where a potential heap-use-after free
    happened. (CVE-2026-15442)

  - In wolfSSL versions 5.7.2 through 5.9.2 there is a client-side implementation flaw in RFC 6961, multiple
    OCSP response stapling, which can lead to certificate forgery. When a wolfSSL client enables OCSP stapling
    with the HAVE_CERTIFICATE_STATUS_REQUEST_V2 feature and calls wolfSSL_UseOCSPStaplingV2(ssl,
    WOLFSSL_CSR2_OCSP_MULTI, options), the client accepts any certificate in the peer's chain as a certificate
    authority without verifying that the certificate is actually authorized to act as one. This means that an
    attacker who possesses any certificate that chains to a CA trusted by the client (along with its private
    key) can forge certificates for arbitrary identities that will be accepted as valid by the client. The end
    entity certificate of the server is stored in the persistent trust store, affecting subsequent connections
    that reuse the context even when OCSP multi usage is not employed. Found by internal wolfSSL testing.
    (CVE-2026-89102)

  - wolfSSL versions 5.9.2 and earlier contain a flaw in the X.509 certificate validation logic where it fails
    to properly enforce NameConstraints extensions when there is an unconstrained CA tier between a name-
    constrained intermediate CA and the leaf certificate. wolfSSL incorrectly accepted certificates for
    hostnames they shouldn't be allowed to cover, due to a chain-walking state-machine bug that resets the
    validation state when encountering an intermediate without NameConstraints, thereby bypassing
    cryptographic delegation controls. This defect exists in the default build configuration that makes use of
    certificates where name constraint extensions are used. Thanks to Jack Lloyd, PathDiff, and Ben Smyth for
    reporting the issue. (CVE-2026-89133)

Linux/Unix 主机中安装的一个或多个程序包受到一个漏洞影响，而供应商没有提供补丁程序。

  - 使用 RPK（原始公钥）时，TLS 1.21.3 和 DTLS 1.2 连接的客户端可接受未经请求的 server_cert_type=RawPublicKey，从而允许恶意或行为不当的服务器绕过认证。RPK 默认关闭，仅在 OR 或 --enable-distro AKA --enable-all HAVE_RPK版本中--enable-rpk启用。（CVE-2026-89136）

请注意，Nessus 依赖供应商报告的程序包是否存在进行判断。

Linux/Unix 主機上安裝了一個或多個受到弱點影響的套件，且廠商未提供可用的修補程式。

  - 使用 RPK （原始公開金鑰） 時，TLS 1.2的 1.3 用戶端和 DTLS 1.2 連線可能會接受未經請求的 server_cert_type=RawPublicKey，這允許惡意或行為不當的伺服器繞過驗證。RPK 預設為關閉狀態，且僅在 OR 或 --enable-distro AKA --enable-all HAVE_RPK組建中--enable-rpk啟用。（CVE-2026-89136）

請注意，Nessus 的判定取決於廠商所報告的套件是否存在。

Linux/Unix ホストには、ベンダーが提供するパッチが利用できない脆弱性の影響を受ける複数のパッケージがインストールされています。

  - RPK(未加工公開鍵)を使用するとき、TLS 1.2、 1.3 および DTLS 1.2 接続のクライアント側が、未承諾の server_cert_type=RawPublicKey を受け入れることがあり、これによって悪意のある、または不正な動作をしているサーバーが認証をバイパスする可能性があります。RPKはデフォルトでオフになっており、 --enable-rpk または --enable-all または --enable-distro (別名HAVE_RPKビルド)でのみ有効です。(CVE-2026-89136)

Nessus は、ベンダーから報告されたパッケージの存在に依存していることに注意してください。

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - When using RPK (Raw Public Key), the client side of a TLS 1.2, 1.3 and DTLS 1.2 connection could accept an     unsolicited server_cert_type=RawPublicKey which allowed a malicious or misbehaving server to bypass     authentication. RPK is off by default and only enabled in --enable-rpk OR --enable-all OR --enable-distro     AKA HAVE_RPK builds. (CVE-2026-89136)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	Name	Product	Family	Published	Updated	Severity
474888	Alpine: multiple wolfssl packages: security update to 5.9.4-r0	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	10/16/2026	10/16/2026	high
474888	Alpine: multiple wolfssl packages: security update to 5.9.4-r0	Tenable Cloud Security	Alpine Linux Local Security Checks	10/16/2026	10/16/2026	high
350873	Linux Distros 未修补的漏洞：CVE-2026-89136	Nessus	Misc.	9/28/2026	10/3/2026	high
350873	Linux Distros 未修補弱點：CVE-2026-89136	Nessus	Misc.	9/28/2026	10/3/2026	high
350873	Linux Distros のパッチ未適用の脆弱性: CVE-2026-89136	Nessus	Misc.	9/28/2026	10/3/2026	high
350873	Linux Distros Unpatched Vulnerability : CVE-2026-89136	Nessus	Misc.	9/28/2026	10/3/2026	high

Detections

Analytics

Plugins Search

high

high

high

high

high

high