undici 的缓存拦截器文档声称只有“安全”的 HTTP 方法会被缓存,但其跳过缓存的逻辑是通过从安全方法集合中减去配置的方法来构建的,导致诸如 POST、PUT 或 DELETE 等“非安全”方法永远不会被列入跳过缓存列表,而是直接落入完整的缓存读取路径。此外,响应存储的门槛也缺乏方法检查,因此针对非安全请求的响应如果被认为是可启发式缓存的,或携带了显式的 指令,也会被存入缓存,并在后续从缓存中重放。由于来自远程源站的响应头是不可信的,源站可以首次返回一个可缓存的状态码,随后客户端对该路径发起的后续会改变状态(
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
| # | POC Description | Source Link | Shenlong Link |
|---|
No public POC found.
Login to generate AI POC| CVE-2026-19534 | 7.5 HIGH | undici vulnerable to Denial of Service via unrequested WebSocket subprotocol |
| CVE-2026-85152 | 7.4 HIGH | undici vulnerable to cross-origin cache poisoning via missing origin isolation in intercep |
| CVE-2026-84961 | 7.4 HIGH | undici vulnerable to TLS certificate validation bypass via dropped connect options in Bala |
| CVE-2026-84933 | 6.5 MEDIUM | undici vulnerable to cross-user cookie disclosure via Set-Cookie caching in shared caches |
| CVE-2026-85024 | 5.9 MEDIUM | undici vulnerable to Denial of Service via unhandled error in WebSocket permessage-deflate |
| CVE-2026-85014 | 5.9 MEDIUM | undici vulnerable to Denial of Service via WebSocketStream unclean close |
| CVE-2026-18149 | 5.9 MEDIUM | undici vulnerable to Denial of Service via orphaned RetryHandler response body |
| CVE-2026-84890 | 5.9 MEDIUM | undici vulnerable to Denial of Service via unbounded decompression of compressed responses |
| CVE-2026-84947 | 3.7 LOW | undici vulnerable to response truncation via oversized chunked responses in the dump inter |
| CVE-2026-18540 | 3.7 LOW | undici vulnerable to downstream response splitting via retry interceptor |
No comments yet