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

  - 在 childTextNodesAreLiteral 中，一旦找到 HTML 整合點，先前向上走樹就會停在最近的外部祖先處。不過，該整合點本身可能是被寄養到外部命名空間中的元素的後代 （例如 <mglyph> 或 <malignmark> 寄養於 <mtext>），導致剖析器在重新剖析轉譯的輸出時解析不同外部命名空間中的子樹狀結構。繼續遍歷完整的上階鏈結，並驗證從非空白命名空間的每個轉換是否發生在 HTML 整合點，再發出文字文字。（CVE-2026-97045）

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

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

  - 在 childTextNodesAreLiteral 中，以前，一旦找到 HTML 集成点，沿着树向上走会在最近的外来祖先处停止。但是，该集成点本身可能是寄养到外部命名空间（例如 <mglyph> 或 <malignmark> 托管在 <mtext>外部命名空间）中的元素的后代，导致解析器在重新解析呈现的输出时解析不同外部命名空间中的子树。继续遍历完整的祖先链，并验证从非空命名空间的每次转换是否发生在 HTML 集成点，然后再发出文字文本。（CVE-2026-97045）

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

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

  - childTextNodesAreLiteral で、以前は HTML 統合ポイントが見つかると、最も近い外部の祖先でツリーを登ると停止しました。ただし、その統合ポイント自体は、外部の名前空間 (<mglyph> や <mtext> の下で <malignmark> など) に育成された要素の子孫である可能性があり、これによってパーサーは、レンダリングされた出力を再解析するときに、別の外部名前空間でサブツリーを解決します。完全な祖先チェーンを引き続き実行し、空でない名前空間からのすべての遷移が、リテラルテキストを出力する前にHTML統合ポイントで発生することを確認します。(CVE-2026-97045)

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

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

  - In childTextNodesAreLiteral, walking up the tree previously stopped at the nearest foreign ancestor once     an HTML integration point was found. However, that integration point may itself be a descendant of an     element that was foster-parented into a foreign namespace (such as <mglyph> or <malignmark> fostered under     <mtext>), causing a parser to resolve the subtree in a different foreign namespace upon re-parsing the     rendered output. Continue walking the full ancestor chain and verify that every transition from a non-     empty namespace occurs at an HTML integration point before emitting literal text. (CVE-2026-97045)

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

The version of docker installed on the remote host is prior to 25.0.18-1. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2NITRO-ENCLAVES-2026-133 advisory.

    eStargz layer decoder in the estartgz package contains a vulnerability that an input containing a cyclic     hardlink crashes the process with Go's unrecoverable stack overflow error. Stargz Snapshotter with the     default configuration relies on that function so pulling an eStargz image containing a muliciously crafted     layer with a cyclic hardlink crashes the Stargz Snapshotter process. (CVE-2026-71482)

    When coalescing adjacent text nodes in addText and fosterParent, appending to an existing TextNode's Data     via string concatenation (n.Data += text) reallocated and copied the accumulated string on every token.
    Inputs containing many short text runs separated by ignored end tags (such as a</x>) caused O(n^2)     allocations and byte copies. Accumulate coalesced text in per-node byte slices during parsing and     materialize Data strings once at the end of parse. (CVE-2026-78661)

    A malicious image can advertise DiffIDs from another image while containing different layer contents. In     affected versions, BuildKit could use the advertised DiffIDs to derive cache and snapshot identity without     validating that they matched the actual layer contents.

    If a BuildKit daemon with shared or persistent cache first processes such a malicious image, a later build     using the victim image may mount the attacker-controlled layer contents as the base image. This can allow     code from the malicious image to run in the victim build, for example by replacing a commonly executed     path such as /bin/sh. The attacker-controlled code may read build secrets mounted into the build, access     other build resources, alter output artifacts, or hang the build.

    The issue affects both regular snapshotters and lazy-pulling snapshotters such as stargz. (CVE-2026-93318)

    In childTextNodesAreLiteral, walking up the tree previously stopped at the nearest foreign ancestor once     an HTML integration point was found. However, that integration point may itself be a descendant of an     element that was foster-parented into a foreign namespace (such as <mglyph> or <malignmark> fostered under     <mtext>), causing a parser to resolve the subtree in a different foreign namespace upon re-parsing the     rendered output. Continue walking the full ancestor chain and verify that every transition from a non-     empty namespace occurs at an HTML integration point before emitting literal text. (CVE-2026-97045)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2026-3428 advisory.

    When coalescing adjacent text nodes in addText and fosterParent, appending to an existing TextNode's Data     via string concatenation (n.Data += text) reallocated and copied the accumulated string on every token.
    Inputs containing many short text runs separated by ignored end tags (such as a</x>) caused O(n^2)     allocations and byte copies. Accumulate coalesced text in per-node byte slices during parsing and     materialize Data strings once at the end of parse. (CVE-2026-78661)

    In childTextNodesAreLiteral, walking up the tree previously stopped at the nearest foreign ancestor once     an HTML integration point was found. However, that integration point may itself be a descendant of an     element that was foster-parented into a foreign namespace (such as <mglyph> or <malignmark> fostered under     <mtext>), causing a parser to resolve the subtree in a different foreign namespace upon re-parsing the     rendered output. Continue walking the full ancestor chain and verify that every transition from a non-     empty namespace occurs at an HTML integration point before emitting literal text. (CVE-2026-97045)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2026-3391 advisory.

    eStargz layer decoder in the estartgz package contains a vulnerability that an input containing a cyclic     hardlink crashes the process with Go's unrecoverable stack overflow error. Stargz Snapshotter with the     default configuration relies on that function so pulling an eStargz image containing a muliciously crafted     layer with a cyclic hardlink crashes the Stargz Snapshotter process. (CVE-2026-71482)

    When coalescing adjacent text nodes in addText and fosterParent, appending to an existing TextNode's Data     via string concatenation (n.Data += text) reallocated and copied the accumulated string on every token.
    Inputs containing many short text runs separated by ignored end tags (such as a</x>) caused O(n^2)     allocations and byte copies. Accumulate coalesced text in per-node byte slices during parsing and     materialize Data strings once at the end of parse. (CVE-2026-78661)

    A malicious image can advertise DiffIDs from another image while containing different layer contents. In     affected versions, BuildKit could use the advertised DiffIDs to derive cache and snapshot identity without     validating that they matched the actual layer contents.

    If a BuildKit daemon with shared or persistent cache first processes such a malicious image, a later build     using the victim image may mount the attacker-controlled layer contents as the base image. This can allow     code from the malicious image to run in the victim build, for example by replacing a commonly executed     path such as /bin/sh. The attacker-controlled code may read build secrets mounted into the build, access     other build resources, alter output artifacts, or hang the build.

    The issue affects both regular snapshotters and lazy-pulling snapshotters such as stargz. (CVE-2026-93318)

    In childTextNodesAreLiteral, walking up the tree previously stopped at the nearest foreign ancestor once     an HTML integration point was found. However, that integration point may itself be a descendant of an     element that was foster-parented into a foreign namespace (such as <mglyph> or <malignmark> fostered under     <mtext>), causing a parser to resolve the subtree in a different foreign namespace upon re-parsing the     rendered output. Continue walking the full ancestor chain and verify that every transition from a non-     empty namespace occurs at an HTML integration point before emitting literal text. (CVE-2026-97045)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of docker installed on the remote host is prior to 25.0.18-1. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2DOCKER-2026-162 advisory.

    eStargz layer decoder in the estartgz package contains a vulnerability that an input containing a cyclic     hardlink crashes the process with Go's unrecoverable stack overflow error. Stargz Snapshotter with the     default configuration relies on that function so pulling an eStargz image containing a muliciously crafted     layer with a cyclic hardlink crashes the Stargz Snapshotter process. (CVE-2026-71482)

    When coalescing adjacent text nodes in addText and fosterParent, appending to an existing TextNode's Data     via string concatenation (n.Data += text) reallocated and copied the accumulated string on every token.
    Inputs containing many short text runs separated by ignored end tags (such as a</x>) caused O(n^2)     allocations and byte copies. Accumulate coalesced text in per-node byte slices during parsing and     materialize Data strings once at the end of parse. (CVE-2026-78661)

    A malicious image can advertise DiffIDs from another image while containing different layer contents. In     affected versions, BuildKit could use the advertised DiffIDs to derive cache and snapshot identity without     validating that they matched the actual layer contents.

    If a BuildKit daemon with shared or persistent cache first processes such a malicious image, a later build     using the victim image may mount the attacker-controlled layer contents as the base image. This can allow     code from the malicious image to run in the victim build, for example by replacing a commonly executed     path such as /bin/sh. The attacker-controlled code may read build secrets mounted into the build, access     other build resources, alter output artifacts, or hang the build.

    The issue affects both regular snapshotters and lazy-pulling snapshotters such as stargz. (CVE-2026-93318)

    In childTextNodesAreLiteral, walking up the tree previously stopped at the nearest foreign ancestor once     an HTML integration point was found. However, that integration point may itself be a descendant of an     element that was foster-parented into a foreign namespace (such as <mglyph> or <malignmark> fostered under     <mtext>), causing a parser to resolve the subtree in a different foreign namespace upon re-parsing the     rendered output. Continue walking the full ancestor chain and verify that every transition from a non-     empty namespace occurs at an HTML integration point before emitting literal text. (CVE-2026-97045)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of docker installed on the remote host is prior to 25.0.18-1. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2ECS-2026-157 advisory.

    eStargz layer decoder in the estartgz package contains a vulnerability that an input containing a cyclic     hardlink crashes the process with Go's unrecoverable stack overflow error. Stargz Snapshotter with the     default configuration relies on that function so pulling an eStargz image containing a muliciously crafted     layer with a cyclic hardlink crashes the Stargz Snapshotter process. (CVE-2026-71482)

    When coalescing adjacent text nodes in addText and fosterParent, appending to an existing TextNode's Data     via string concatenation (n.Data += text) reallocated and copied the accumulated string on every token.
    Inputs containing many short text runs separated by ignored end tags (such as a</x>) caused O(n^2)     allocations and byte copies. Accumulate coalesced text in per-node byte slices during parsing and     materialize Data strings once at the end of parse. (CVE-2026-78661)

    A malicious image can advertise DiffIDs from another image while containing different layer contents. In     affected versions, BuildKit could use the advertised DiffIDs to derive cache and snapshot identity without     validating that they matched the actual layer contents.

    If a BuildKit daemon with shared or persistent cache first processes such a malicious image, a later build     using the victim image may mount the attacker-controlled layer contents as the base image. This can allow     code from the malicious image to run in the victim build, for example by replacing a commonly executed     path such as /bin/sh. The attacker-controlled code may read build secrets mounted into the build, access     other build resources, alter output artifacts, or hang the build.

    The issue affects both regular snapshotters and lazy-pulling snapshotters such as stargz. (CVE-2026-93318)

    In childTextNodesAreLiteral, walking up the tree previously stopped at the nearest foreign ancestor once     an HTML integration point was found. However, that integration point may itself be a descendant of an     element that was foster-parented into a foreign namespace (such as <mglyph> or <malignmark> fostered under     <mtext>), causing a parser to resolve the subtree in a different foreign namespace upon re-parsing the     rendered output. Continue walking the full ancestor chain and verify that every transition from a non-     empty namespace occurs at an HTML integration point before emitting literal text. (CVE-2026-97045)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2026-3450 advisory.

    Go JOSE provides an implementation of the Javascript Object Signing and Encryption set of standards in Go,     including support for JSON Web Encryption (JWE), JSON Web Signature (JWS), and JSON Web Token (JWT)     standards. Prior to 4.1.5, decrypting untrusted JWE ciphertext with A128CBC-HS256, A192CBC-HS384, or     A256CBC-HS512 can pass an empty ciphertext buffer to CBC-HMAC unpadding. Insufficient validation allows     the empty buffer to be indexed, causing a panic and denial of service. Applications that decrypt attacker-     controlled ciphertext with one of these content-encryption algorithms are affected. This issue is fixed in     version 4.1.5. (CVE-2026-116585)

    Go JOSE provides an implementation of the Javascript Object Signing and Encryption set of standards in Go,     including support for JSON Web Encryption (JWE), JSON Web Signature (JWS), and JSON Web Token (JWT)     standards. Prior to 4.1.5, parsing attacker-controlled JSON through go-jose allows deeply nested arrays or     objects to exceed Go's stack limit. The resulting stack overflow crashes the application and permits     denial of service in applications that parse untrusted JSON through go-jose. This issue is fixed in     version 4.1.5. (CVE-2026-116586)

    Go JOSE provides an implementation of the Javascript Object Signing and Encryption set of standards in Go,     including support for JSON Web Encryption (JWE), JSON Web Signature (JWS), and JSON Web Token (JWT)     standards. Prior to 4.1.6, go-jose parses attacker-controlled RSA modulus and prime values from JWKs     without enforcing size and consistency bounds before passing them to crypto/rsa.PrivateKey.Validate. On Go     1.24 and later, crafted large or degenerate RSA parameters can make that validation consume cubic CPU     time, allowing remote denial of service in applications that parse JWKs from untrusted sources. This issue     is fixed in version 4.1.6. (CVE-2026-116587)

    compress provides various compression algorithms. Prior to 1.20.2, the zstd DecodeAll and streaming     decoder paths can panic when a crafted two-block frame reaches huff0.ReadTable with an FSE normalized     count of 32768 that readNCount stores in int16 as -32768. The wrapped count allows buildDtable to retain     stale fse.Scratch decode-table state from the prior block, and nextFast then derives an out-of-range state     and indexes beyond the table instead of returning a decode error. Both blocks are required to preserve and     then reuse the stale state, allowing untrusted zstd input to crash an application. This issue is fixed in     version 1.20.2. (CVE-2026-116591)

    The `github.com/moby/sys/user` package provides Go utilities for parsing and looking up entries in Unix-     style user and group database files. Versions before 0.4.1 do not sufficiently limit entries when parsing     `/etc/passwd`- or `/etc/group`-style files, allowing an attacker who can supply a specially crafted file     to cause excessive memory consumption and potentially terminate the affected process due to an out-of-     memory condition. This issue is patched in version 0.4.1. As a workaround, avoid parsing attacker-     controlled user or group database files, or validate and limit untrusted input before parsing it.
    (CVE-2026-61801)

    eStargz layer decoder in the estartgz package contains a vulnerability that an input containing a cyclic     hardlink crashes the process with Go's unrecoverable stack overflow error. Stargz Snapshotter with the     default configuration relies on that function so pulling an eStargz image containing a muliciously crafted     layer with a cyclic hardlink crashes the Stargz Snapshotter process. (CVE-2026-71482)

    When coalescing adjacent text nodes in addText and fosterParent, appending to an existing TextNode's Data     via string concatenation (n.Data += text) reallocated and copied the accumulated string on every token.
    Inputs containing many short text runs separated by ignored end tags (such as a</x>) caused O(n^2)     allocations and byte copies. Accumulate coalesced text in per-node byte slices during parsing and     materialize Data strings once at the end of parse. (CVE-2026-78661)

    A flaw was found in the containers/storage library. A crafted tar archive containing a malicious whiteout     header (e.g. victim/.wh.) can cause the extraction destination directory to be replaced with an arbitrary     file when processed by storage/pkg/archive.UnpackLayer, ApplyLayer, or ApplyUncompressedLayer.
    (CVE-2026-79699)

    In childTextNodesAreLiteral, walking up the tree previously stopped at the nearest foreign ancestor once     an HTML integration point was found. However, that integration point may itself be a descendant of an     element that was foster-parented into a foreign namespace (such as <mglyph> or <malignmark> fostered under     <mtext>), causing a parser to resolve the subtree in a different foreign namespace upon re-parsing the     rendered output. Continue walking the full ancestor chain and verify that every transition from a non-     empty namespace occurs at an HTML integration point before emitting literal text. (CVE-2026-97045)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote openSUSE 16 host has a package installed that is affected by multiple vulnerabilities as referenced in the openSUSE-SU-2026:22273-1 advisory.

    Update to version 0.76.2.

    Security issues fixed:

    - CVE-2026-97045: golang.org/x/net/html: missing checks during ancestor namespace transitions when     rendering raw       text can cause parser differentials (bsc#1289868).
    - CVE-2026-116585,CVE-2026-116586,CVE-2026-116587: github.com/go-jose/go-jose/v4: multiple security issues     in       github.com/go-jose/go-jose before 4.1.6 (bsc#1288377).

    Other updates and bugfixes:

    - Update `x/sys` to 0.50.0 to fix ppc64le syscall handling regression.
    - Version 0.76.2:
     * fix(deps): bump `golang.org/x/net` from 0.61.0 to 0.62.0 [backport: release/v0.76] (#11554)
     * chore(deps): bump the common group across 1 directory with 14 updates [backport: release/v0.76]     (#11555)
     * fix(deps): bump `github.com/go-jose/go-jose/v4` from 4.1.5 to 4.1.6 [backport: release/v0.76] (#11553)
     * fix(deps): bump `alpine` to 3.24.3 in container images [backport: release/v0.76] (#11551)

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of amazon-ssm-agent installed on the remote host is prior to 3.3.5828.0-1. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2-2026-4101 advisory.

    When coalescing adjacent text nodes in addText and fosterParent, appending to an existing TextNode's Data     via string concatenation (n.Data += text) reallocated and copied the accumulated string on every token.
    Inputs containing many short text runs separated by ignored end tags (such as a</x>) caused O(n^2)     allocations and byte copies. Accumulate coalesced text in per-node byte slices during parsing and     materialize Data strings once at the end of parse. (CVE-2026-78661)

    In childTextNodesAreLiteral, walking up the tree previously stopped at the nearest foreign ancestor once     an HTML integration point was found. However, that integration point may itself be a descendant of an     element that was foster-parented into a foreign namespace (such as <mglyph> or <malignmark> fostered under     <mtext>), causing a parser to resolve the subtree in a different foreign namespace upon re-parsing the     rendered output. Continue walking the full ancestor chain and verify that every transition from a non-     empty namespace occurs at an HTML integration point before emitting literal text. (CVE-2026-97045)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2026-3451 advisory.

    Go JOSE provides an implementation of the Javascript Object Signing and Encryption set of standards in Go,     including support for JSON Web Encryption (JWE), JSON Web Signature (JWS), and JSON Web Token (JWT)     standards. Prior to 4.1.5, decrypting untrusted JWE ciphertext with A128CBC-HS256, A192CBC-HS384, or     A256CBC-HS512 can pass an empty ciphertext buffer to CBC-HMAC unpadding. Insufficient validation allows     the empty buffer to be indexed, causing a panic and denial of service. Applications that decrypt attacker-     controlled ciphertext with one of these content-encryption algorithms are affected. This issue is fixed in     version 4.1.5. (CVE-2026-116585)

    Go JOSE provides an implementation of the Javascript Object Signing and Encryption set of standards in Go,     including support for JSON Web Encryption (JWE), JSON Web Signature (JWS), and JSON Web Token (JWT)     standards. Prior to 4.1.5, parsing attacker-controlled JSON through go-jose allows deeply nested arrays or     objects to exceed Go's stack limit. The resulting stack overflow crashes the application and permits     denial of service in applications that parse untrusted JSON through go-jose. This issue is fixed in     version 4.1.5. (CVE-2026-116586)

    Go JOSE provides an implementation of the Javascript Object Signing and Encryption set of standards in Go,     including support for JSON Web Encryption (JWE), JSON Web Signature (JWS), and JSON Web Token (JWT)     standards. Prior to 4.1.6, go-jose parses attacker-controlled RSA modulus and prime values from JWKs     without enforcing size and consistency bounds before passing them to crypto/rsa.PrivateKey.Validate. On Go     1.24 and later, crafted large or degenerate RSA parameters can make that validation consume cubic CPU     time, allowing remote denial of service in applications that parse JWKs from untrusted sources. This issue     is fixed in version 4.1.6. (CVE-2026-116587)

    compress provides various compression algorithms. Prior to 1.20.2, the zstd DecodeAll and streaming     decoder paths can panic when a crafted two-block frame reaches huff0.ReadTable with an FSE normalized     count of 32768 that readNCount stores in int16 as -32768. The wrapped count allows buildDtable to retain     stale fse.Scratch decode-table state from the prior block, and nextFast then derives an out-of-range state     and indexes beyond the table instead of returning a decode error. Both blocks are required to preserve and     then reuse the stale state, allowing untrusted zstd input to crash an application. This issue is fixed in     version 1.20.2. (CVE-2026-116591)

    The `github.com/moby/sys/user` package provides Go utilities for parsing and looking up entries in Unix-     style user and group database files. Versions before 0.4.1 do not sufficiently limit entries when parsing     `/etc/passwd`- or `/etc/group`-style files, allowing an attacker who can supply a specially crafted file     to cause excessive memory consumption and potentially terminate the affected process due to an out-of-     memory condition. This issue is patched in version 0.4.1. As a workaround, avoid parsing attacker-     controlled user or group database files, or validate and limit untrusted input before parsing it.
    (CVE-2026-61801)

    eStargz layer decoder in the estartgz package contains a vulnerability that an input containing a cyclic     hardlink crashes the process with Go's unrecoverable stack overflow error. Stargz Snapshotter with the     default configuration relies on that function so pulling an eStargz image containing a muliciously crafted     layer with a cyclic hardlink crashes the Stargz Snapshotter process. (CVE-2026-71482)

    When coalescing adjacent text nodes in addText and fosterParent, appending to an existing TextNode's Data     via string concatenation (n.Data += text) reallocated and copied the accumulated string on every token.
    Inputs containing many short text runs separated by ignored end tags (such as a</x>) caused O(n^2)     allocations and byte copies. Accumulate coalesced text in per-node byte slices during parsing and     materialize Data strings once at the end of parse. (CVE-2026-78661)

    A flaw was found in the containers/storage library. A crafted tar archive containing a malicious whiteout     header (e.g. victim/.wh.) can cause the extraction destination directory to be replaced with an arbitrary     file when processed by storage/pkg/archive.UnpackLayer, ApplyLayer, or ApplyUncompressedLayer.
    (CVE-2026-79699)

    In childTextNodesAreLiteral, walking up the tree previously stopped at the nearest foreign ancestor once     an HTML integration point was found. However, that integration point may itself be a descendant of an     element that was foster-parented into a foreign namespace (such as <mglyph> or <malignmark> fostered under     <mtext>), causing a parser to resolve the subtree in a different foreign namespace upon re-parsing the     rendered output. Continue walking the full ancestor chain and verify that every transition from a non-     empty namespace occurs at an HTML integration point before emitting literal text. (CVE-2026-97045)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	名稱	產品	系列	已發布	已更新	嚴重性
372983	Linux Distros 未修補弱點：CVE-2026-97045	Nessus	Misc.	2026/10/28	2026/11/5	medium
372983	Linux Distros 未修补的漏洞：CVE-2026-97045	Nessus	Misc.	2026/10/28	2026/11/5	medium
372983	Linux Distros のパッチ未適用の脆弱性: CVE-2026-97045	Nessus	Misc.	2026/10/28	2026/11/5	medium
372983	Linux Distros Unpatched Vulnerability : CVE-2026-97045	Nessus	Misc.	2026/10/28	2026/11/5	medium
377901	Amazon Linux 2 : docker (ALASNITRO-ENCLAVES-2026-133)	Nessus	Amazon Linux Local Security Checks	2026/11/9	2026/11/9	high
379816	Amazon Linux 2023 : amazon-ssm-agent (ALAS2023-2026-3428)	Nessus	Amazon Linux Local Security Checks	2026/11/12	2026/11/12	high
377915	Amazon Linux 2023 : docker (ALAS2023-2026-3391)	Nessus	Amazon Linux Local Security Checks	2026/11/9	2026/11/9	high
377921	Amazon Linux 2 : docker (ALASDOCKER-2026-162)	Nessus	Amazon Linux Local Security Checks	2026/11/9	2026/11/9	high
377952	Amazon Linux 2 : docker (ALASECS-2026-157)	Nessus	Amazon Linux Local Security Checks	2026/11/9	2026/11/9	high
379853	Amazon Linux 2023 : skopeo, skopeo-tests (ALAS2023-2026-3450)	Nessus	Amazon Linux Local Security Checks	2026/11/12	2026/11/12	high
381206	openSUSE 16 Security Update : trivy (openSUSE-SU-2026:22273-1)	Nessus	SuSE Local Security Checks	2026/11/14	2026/11/14	medium
379891	Amazon Linux 2 : amazon-ssm-agent (ALAS-2026-4101)	Nessus	Amazon Linux Local Security Checks	2026/11/12	2026/11/12	high
379846	Amazon Linux 2023 : buildah (ALAS2023-2026-3451)	Nessus	Amazon Linux Local Security Checks	2026/11/12	2026/11/12	high

偵測

搜尋 Plugin

medium

medium

medium

medium

high

high

high

high

high

high

medium

high

high