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

  - 合併 addText 和 fosterParent 中的相鄰文字節點時，透過字串串連 （n.Data += text） 附加至現有 TextNode 的資料，重新配置並複製每個權杖上的累積字串。
    包含許多以忽略結束標籤分隔的短文字執行的輸入 （例如 a</x>） 會導致 O（n^2） 配置和位元組副本。在剖析期間，在每個節點位元組切片中累積合併的文字，並在剖析結束時具體化資料字串一次。（CVE-2026-78661）

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

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

  - 合并 addText 和 fosterParent 中的相邻文本节点时，通过字符串连接 （n.Data += text） 附加到现有 TextNode 的数据，重新分配并复制每个标记上的累积字符串。
    包含许多由被忽略的结束标记（如 a</x>）分隔的短文本运行的输入导致 O（n^2） 分配和字节复制。解析期间在每个节点的字节切片中累积合并文本，并在解析结束时具体化一次数据字符串。（CVE-2026-78661）

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

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

  - addText と fosterParent の隣接するテキストノードを合体するとき、文字列連結(n.Data += text)により既存の TextNode のデータに追加することで、各トークンで累積された文字列が再割り当てされ、コピーされます。
    無視された終了タグ(a</x> など)で区切られた多数の短いテキストを含む入力により、O(n^2) 割り当てとバイトコピーが引き起こされました。解析中に結合したテキストをノードバイト単位のスライスに集積し、解析の最後にデータ文字列を一度具体化します。(CVE-2026-78661)

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

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

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

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

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.

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.

ID	名前	製品	ファミリー	公開日	更新日	深刻度
373000	Linux Distros 未修補弱點：CVE-2026-78661	Nessus	Misc.	2026/10/28	2026/11/5	high
373000	Linux Distros 未修补的漏洞：CVE-2026-78661	Nessus	Misc.	2026/10/28	2026/11/5	high
373000	Linux Distros のパッチ未適用の脆弱性: CVE-2026-78661	Nessus	Misc.	2026/10/28	2026/11/5	high
373000	Linux Distros Unpatched Vulnerability : CVE-2026-78661	Nessus	Misc.	2026/10/28	2026/11/5	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
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

検出

プラグインの検索

high

high

high

high

high

high

high

high

high