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 主機上安裝了一個或多個受到弱點影響的套件，且廠商未提供可用的修補程式。

  - 在使用 （D）TLS 的所有組建中，包括預設組建，在 TLS 關閉期間會有一系列條件狀態，這可能會導致釋放後堆積使用。如果應用程式最終獲得部分 wolfSSL_read（），有時是由傳入的小型使用者緩衝區引起的，然後呼叫 wolfSSL_shutdown 進行雙向關閉，並再次嘗試wolfSSL_read （），而對等體在關機期間繼續嘗試傳送資料，則會導致發生潛在堆積使用釋放後的狀態。（CVE-2026-15442）

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

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

  - 在使用 （D）TLS 的所有版本（包括默认版本）中，TLS 关闭期间存在一系列条件状态，可导致堆释放后使用。如果应用程序最终获得部分 wolfSSL_read（），有时是由传入的小用户缓冲区导致，然后调用 wolfSSL_shutdown 进行双向关闭并再次尝试 wolfSSL_read（），而对等机在关机期间继续尝试发送数据，则会导致发生潜在堆释放后使用的情况。（CVE-2026-15442）

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

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

  - デフォルトのビルドを含めて、(D)TLS を使用するすべてのビルドでは、TLS シャットダウン中に一連の条件付き状態があり、これによってヒープの use-after-free が発生することがあります。アプリケーションが部分的な wolfSSL_read() を取得すると(これは、小さなユーザーバッファが渡されたことが原因でことがあります)、双方向クローズのために wolfSSL_shutdown を呼び出し、シャットダウン中にピアがデータ送信を引き続き試行する間に再度 wolfSSL_read() を試行すると、潜在的なヒープ use-after-free が発生する状態につながる可能性があります。(CVE-2026-15442)

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

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

  - 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)

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
350849	Linux Distros 未修補弱點：CVE-2026-15442	Nessus	Misc.	9/27/2026	10/5/2026	low
350849	Linux Distros 未修补的漏洞：CVE-2026-15442	Nessus	Misc.	9/27/2026	10/5/2026	low
350849	Linux Distros のパッチ未適用の脆弱性: CVE-2026-15442	Nessus	Misc.	9/27/2026	10/5/2026	low
350849	Linux Distros Unpatched Vulnerability : CVE-2026-15442	Nessus	Misc.	9/27/2026	10/5/2026	low

Detections

Analytics

Plugins Search

high

high

low

low

low

low