<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Response-Confusion — PoC Archive</title><link>https://poc.intelseclab.com/tags/response-confusion/</link><description>Latest proof-of-concept entries.</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 17 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://poc.intelseclab.com/tags/response-confusion/index.xml" rel="self" type="application/rss+xml"/><item><title>Next.js RSC Response Cache Poisoning (CVE-2026-44576)</title><link>https://poc.intelseclab.com/pocs/web/2026-05-17_nextjs-rsc-response-cache-poisoning/</link><pubDate>Sun, 17 May 2026 00:00:00 +0000</pubDate><guid>https://poc.intelseclab.com/pocs/web/2026-05-17_nextjs-rsc-response-cache-poisoning/</guid><description>Medium severity (CVSS 5.4) — web · CVE-2026-44576. Status: Weaponized. Affects: Next.js App Router deployments using React Server Components (RSC) behind shared caches. Tags: cache-poisoning, RSC, response-confusion, Next.js, shared-cache, unauthenticated.</description><category>web</category><category>Medium</category><category>cache-poisoning</category><category>RSC</category><category>response-confusion</category><category>Next.js</category><category>shared-cache</category><category>unauthenticated</category></item></channel></rss>