<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
  <channel>
    <title>CVE 追蹤：攻擊手法（smuggling、cache poisoning、HTTP/2 DoS、WAF bypass）</title>
    <link>https://jared-lee-cw.github.io/cve-feed/</link>
    <description>不限產品，描述中出現 CDN/DDoS/WAF 相關攻擊手法，CVSS ≥ 7</description>
    <language>zh-TW</language>
    <lastBuildDate>Fri, 23 Oct 2026 06:27:21 +0000</lastBuildDate>
    <atom:link href="https://jared-lee-cw.github.io/cve-feed/attacks.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>[HIGH 7.5] CVE-2026-115482 — Amplification</title>
      <link>https://nvd.nist.gov/vuln/detail/CVE-2026-115482</link>
      <guid isPermaLink="false">CVE-2026-115482</guid>
      <pubDate>Thu, 22 Oct 2026 19:17:48 +0000</pubDate>
      <description>&lt;p&gt;In lsquic before 4.9.0, the HTTP/3 implementation can use an excessive amount of memory because the number of buffered header sets is not limited, as demonstrated by a QPACK amplification attack. This is related to header_out_dynamic_entry and es_max_header_list_size.&lt;/p&gt;&lt;ul&gt;&lt;li&gt;CVSS 3.1：&lt;b&gt;7.5 HIGH&lt;/b&gt;（CNA）&lt;br&gt;&lt;code&gt;CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H&lt;/code&gt;&lt;/li&gt;&lt;li&gt;CWE：CWE-770&lt;/li&gt;&lt;li&gt;比對：Amplification（關鍵字 amplification attack|reflection attack）&lt;/li&gt;&lt;li&gt;NVD 狀態：Deferred｜發布 2026-10-22｜最後修改 2026-10-22T19:17&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;參考連結：&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;a href="https://foxio.io/blog/header-accordions-qpack-amplification-attacks-against-http-3-servers"&gt;https://foxio.io/blog/header-accordions-qpack-amplification-attacks-against-http-3-servers&lt;/a&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="https://github.com/litespeedtech/lsquic/compare/v4.8.2...v4.9.0"&gt;https://github.com/litespeedtech/lsquic/compare/v4.8.2...v4.9.0&lt;/a&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="https://github.com/litespeedtech/lsquic/pull/666"&gt;https://github.com/litespeedtech/lsquic/pull/666&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;</description>
      <category>HIGH</category>
      <category>Amplification</category>
      <category>CWE-770</category>
    </item>
    <item>
      <title>[CRITICAL 9.3] CVE-2026-111816 — Apache Traffic Server, Cache poisoning</title>
      <link>https://nvd.nist.gov/vuln/detail/CVE-2026-111816</link>
      <guid isPermaLink="false">CVE-2026-111816</guid>
      <pubDate>Thu, 22 Oct 2026 16:56:52 +0000</pubDate>
      <description>&lt;p&gt;Apache Traffic Server forwarded a malformed 302 response that should have been rejected as a parse error, because the Transfer-Encoding: chunked carve-out bypassed the rejection path. A response that two peers can read differently is then stored and served, allowing cache poisoning and response-framing desync.



This issue affects Apache Traffic Server: from 8.0.0 through 8.1.11, from 9.0.0 through 9.2.15, from 10.0.0 through 10.1.4, 10.2.0.



Users are recommended to upgrade to version 9.2.16, 10.1.5, or 10.2.1, which fix the issue.&lt;/p&gt;&lt;ul&gt;&lt;li&gt;CVSS 3.1：&lt;b&gt;9.3 CRITICAL&lt;/b&gt;（CNA）&lt;br&gt;&lt;code&gt;CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:N&lt;/code&gt;&lt;/li&gt;&lt;li&gt;CWE：CWE-444&lt;/li&gt;&lt;li&gt;比對：Apache Traffic Server（關鍵字 Apache Traffic Server）；Cache poisoning（關鍵字 cache poisoning）&lt;/li&gt;&lt;li&gt;NVD 狀態：Awaiting Analysis｜發布 2026-10-21｜最後修改 2026-10-22T16:56&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;參考連結：&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;a href="https://lists.apache.org/thread/r95dq29ywcd1f4x30snxlqmb12z4s4kc"&gt;https://lists.apache.org/thread/r95dq29ywcd1f4x30snxlqmb12z4s4kc&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;</description>
      <category>CRITICAL</category>
      <category>Apache Traffic Server</category>
      <category>Cache poisoning</category>
      <category>CWE-444</category>
    </item>
    <item>
      <title>[CRITICAL 9.3] CVE-2026-111809 — Apache Traffic Server, Request smuggling</title>
      <link>https://nvd.nist.gov/vuln/detail/CVE-2026-111809</link>
      <guid isPermaLink="false">CVE-2026-111809</guid>
      <pubDate>Thu, 22 Oct 2026 16:56:52 +0000</pubDate>
      <description>&lt;p&gt;Apache Traffic Server allows request smuggling via HEAD requests that carry Content-Length or Transfer-Encoding.



This issue affects Apache Traffic Server: from 8.0.0 through 8.1.11, from 9.0.0 through 9.2.15, from 10.0.0 through 10.1.4, 10.2.0.



Users are recommended to upgrade to version 9.2.16, 10.1.5, or 10.2.1, which fix the issue.&lt;/p&gt;&lt;ul&gt;&lt;li&gt;CVSS 3.1：&lt;b&gt;9.3 CRITICAL&lt;/b&gt;（CNA）&lt;br&gt;&lt;code&gt;CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:N&lt;/code&gt;&lt;/li&gt;&lt;li&gt;CWE：CWE-444&lt;/li&gt;&lt;li&gt;比對：Apache Traffic Server（關鍵字 Apache Traffic Server）；Request smuggling（關鍵字 request smuggling）&lt;/li&gt;&lt;li&gt;NVD 狀態：Awaiting Analysis｜發布 2026-10-21｜最後修改 2026-10-22T16:56&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;參考連結：&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;a href="https://lists.apache.org/thread/r95dq29ywcd1f4x30snxlqmb12z4s4kc"&gt;https://lists.apache.org/thread/r95dq29ywcd1f4x30snxlqmb12z4s4kc&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;</description>
      <category>CRITICAL</category>
      <category>Apache Traffic Server</category>
      <category>Request smuggling</category>
      <category>CWE-444</category>
    </item>
    <item>
      <title>[CRITICAL 9.1] CVE-2026-109829 — Cache poisoning</title>
      <link>https://nvd.nist.gov/vuln/detail/CVE-2026-109829</link>
      <guid isPermaLink="false">CVE-2026-109829</guid>
      <pubDate>Mon, 19 Oct 2026 20:45:43 +0000</pubDate>
      <description>&lt;p&gt;undici is an HTTP client library for Node.js. In versions 7.0.0 through 7.30.0 and 8.0.0 through 8.12.1, when an originless Agent composes the redirect and cache interceptors in that order with a shared cache store, the cache builds its key from the original request URL before the redirect handler changes the origin, so a response produced after a cross-origin redirect is stored under the original key. An attacker who controls the target of a redirect from a trusted URL can have their response cached under that trusted URL and served to later callers, allowing persistent cache poisoning, and the same key confusion lets a private, non-stored redirect response to a user-specific resource be stored under the original URL and served to a later unauthenticated caller, disclosing private data. Applications are affected only when an originless Agent, a shared cache store, and the redirect-then-cache composition are all used. The issue is fixed in undici 7.30.1 and 8.12.2, which verify the producing origin still matches the cache key and preserve each redirect hop&amp;#x27;s cache-control policy before storing, and users should upgrade to one of those versions or later. As a workaround, compose the cache interceptor before the redirect interceptor, use per-origin dispatchers and cache stores, or disable shared caching on redirect-capable requests.&lt;/p&gt;&lt;ul&gt;&lt;li&gt;CVSS 3.1：&lt;b&gt;9.1 CRITICAL&lt;/b&gt;（NVD）&lt;br&gt;&lt;code&gt;CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N&lt;/code&gt;&lt;/li&gt;&lt;li&gt;CWE：CWE-346, CWE-524&lt;/li&gt;&lt;li&gt;比對：Cache poisoning（關鍵字 cache poisoning）&lt;/li&gt;&lt;li&gt;NVD 狀態：Analyzed｜發布 2026-10-15｜最後修改 2026-10-19T20:45&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;參考連結：&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;a href="https://cna.openjsf.org/security-advisories.html"&gt;https://cna.openjsf.org/security-advisories.html&lt;/a&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="https://github.com/nodejs/undici/security/advisories/GHSA-4w7w-5xrc-9h26"&gt;https://github.com/nodejs/undici/security/advisories/GHSA-4w7w-5xrc-9h26&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;</description>
      <category>CRITICAL</category>
      <category>Cache poisoning</category>
      <category>CWE-346</category>
      <category>CWE-524</category>
    </item>
    <item>
      <title>[HIGH 7.2] CVE-2026-41510 — Coraza, WAF bypass</title>
      <link>https://nvd.nist.gov/vuln/detail/CVE-2026-41510</link>
      <guid isPermaLink="false">CVE-2026-41510</guid>
      <pubDate>Fri, 16 Oct 2026 16:00:33 +0000</pubDate>
      <description>&lt;p&gt;OWASP Coraza WAF is a golang modsecurity compatible web application firewall library. From 3.0.0 until 3.8.1, Coraza silently drops arguments after SecArgumentsLimit in internal/corazawaf/transaction.go, while internal/bodyprocessors/urlencoded.go writes ARGS_POST without enforcing the cap. The flaw is triggered when an unauthenticated attacker sends more arguments than SecArgumentsLimit or supplies bodies that expand beyond the configured argument and flattening budgets. An unauthenticated attacker can flood requests with arguments so excess values are silently omitted from ARGS, ARGS_GET, ARGS_NAMES, ARGS_GET_NAMES, ARGS_POST, or ARGS_PATH before security rules inspect them; affected urlencoded and JSON processing can also consume excessive memory. The omission can bypass WAF rules protecting the downstream application, and unbounded or amplified argument processing can cause memory consumption and service degradation. This issue is fixed in version 3.8.1.&lt;/p&gt;&lt;ul&gt;&lt;li&gt;CVSS 3.1：&lt;b&gt;7.2 HIGH&lt;/b&gt;（CNA）&lt;br&gt;&lt;code&gt;CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:L&lt;/code&gt;&lt;/li&gt;&lt;li&gt;CWE：CWE-693, CWE-770&lt;/li&gt;&lt;li&gt;比對：Coraza（關鍵字 \bCoraza\b）；WAF bypass（關鍵字 \bWAF bypass\b|bypass (the )?(web application firewall|WAF)）&lt;/li&gt;&lt;li&gt;NVD 狀態：Awaiting Analysis｜發布 2026-10-12｜最後修改 2026-10-16T16:00&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;參考連結：&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;a href="https://github.com/corazawaf/coraza/commit/146c2f79f39ad16f13787e7d67ad400f8d8cb9a3"&gt;https://github.com/corazawaf/coraza/commit/146c2f79f39ad16f13787e7d67ad400f8d8cb9a3&lt;/a&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="https://github.com/corazawaf/coraza/commit/b98359bb7e7606c95100dcc7ad490d2d624e6dea"&gt;https://github.com/corazawaf/coraza/commit/b98359bb7e7606c95100dcc7ad490d2d624e6dea&lt;/a&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="https://github.com/corazawaf/coraza/releases/tag/v3.8.1"&gt;https://github.com/corazawaf/coraza/releases/tag/v3.8.1&lt;/a&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="https://github.com/corazawaf/coraza/security/advisories/GHSA-6r3q-mjv7-xr8m"&gt;https://github.com/corazawaf/coraza/security/advisories/GHSA-6r3q-mjv7-xr8m&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;</description>
      <category>HIGH</category>
      <category>Coraza</category>
      <category>WAF bypass</category>
      <category>CWE-693</category>
      <category>CWE-770</category>
    </item>
    <item>
      <title>[HIGH 7.7] CVE-2026-61642 — Squid, Request smuggling</title>
      <link>https://nvd.nist.gov/vuln/detail/CVE-2026-61642</link>
      <guid isPermaLink="false">CVE-2026-61642</guid>
      <pubDate>Fri, 16 Oct 2026 16:00:33 +0000</pubDate>
      <description>&lt;p&gt;Squid is a caching proxy for the Web. From 3.3.0.1 to before 7.6, due to an improper enforcement of behavioral workflow bug, Squid is vulnerable to a Request Smuggling attack against HTTP/1.1 Transfer-Encoding. HTTP header parsing (`src/HttpHeader.cc`) accepted the bare` Transfer-Encoding:` identity form, which the HTTP specification prohibits because any transfer coding must be wrapped within chunked encoding. This problem allows a trusted client to perform an HTTP Request Smuggling attack when HTTP/1.1 is used, bypassing security mechanisms that may be in place between attacker and Squid. When there is an HTTP cache operating prior to the affected Squid, this Request Smuggling attack also allows the attacker to poison that web cache and store arbitrary malicious content at any URL for delivery to other clients&amp;#x27; future requests. This issue is fixed in version 7.6.&lt;/p&gt;&lt;ul&gt;&lt;li&gt;CVSS 3.1：&lt;b&gt;7.7 HIGH&lt;/b&gt;（CNA）&lt;br&gt;&lt;code&gt;CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N&lt;/code&gt;&lt;/li&gt;&lt;li&gt;CWE：CWE-444&lt;/li&gt;&lt;li&gt;比對：Squid（關鍵字 ^\s*Squid is）；Request smuggling（關鍵字 request smuggling）&lt;/li&gt;&lt;li&gt;NVD 狀態：Awaiting Analysis｜發布 2026-10-13｜最後修改 2026-10-16T16:00&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;參考連結：&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;a href="https://github.com/squid-cache/squid/commit/d06f48de8b8cc9a378cb91ecfe8e89b6e81696d2"&gt;https://github.com/squid-cache/squid/commit/d06f48de8b8cc9a378cb91ecfe8e89b6e81696d2&lt;/a&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="https://github.com/squid-cache/squid/commit/d808a7c825a70275113790471135c9c4d547ee51"&gt;https://github.com/squid-cache/squid/commit/d808a7c825a70275113790471135c9c4d547ee51&lt;/a&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="https://github.com/squid-cache/squid/pull/2427"&gt;https://github.com/squid-cache/squid/pull/2427&lt;/a&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="https://github.com/squid-cache/squid/pull/2431"&gt;https://github.com/squid-cache/squid/pull/2431&lt;/a&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="https://github.com/squid-cache/squid/releases/tag/SQUID_7_6"&gt;https://github.com/squid-cache/squid/releases/tag/SQUID_7_6&lt;/a&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="https://github.com/squid-cache/squid/security/advisories/GHSA-537g-4gfh-w7m6"&gt;https://github.com/squid-cache/squid/security/advisories/GHSA-537g-4gfh-w7m6&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;</description>
      <category>HIGH</category>
      <category>Squid</category>
      <category>Request smuggling</category>
      <category>CWE-444</category>
    </item>
  </channel>
</rss>