<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Nghttpx — PoC Archive</title><link>https://poc.intelseclab.com/tags/nghttpx/</link><description>Latest proof-of-concept entries.</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 03 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://poc.intelseclab.com/tags/nghttpx/index.xml" rel="self" type="application/rss+xml"/><item><title>nghttpx HTTP/1.1 Upgrade Request Body Response Queue Poisoning</title><link>https://poc.intelseclab.com/pocs/network/2026-07-03_nghttpx-http-upgrade-queue-poisoning/</link><pubDate>Fri, 03 Jul 2026 00:00:00 +0000</pubDate><guid>https://poc.intelseclab.com/pocs/network/2026-07-03_nghttpx-http-upgrade-queue-poisoning/</guid><description>High severity — network · None assigned as of 2026-07-03. Status: PoC. Affects: nghttp2's nghttpx reverse proxy. Tags: nghttp2, nghttpx, reverse-proxy, request-smuggling, response-queue-poisoning, http-desync, upgrade-request, cache-poisoning.</description><category>network</category><category>High</category><category>nghttp2</category><category>nghttpx</category><category>reverse-proxy</category><category>request-smuggling</category><category>response-queue-poisoning</category><category>http-desync</category><category>upgrade-request</category><category>cache-poisoning</category></item></channel></rss>