hunt-http-smuggling

Detect HTTP request smuggling via front-end and back-end parser inconsistencies.

1|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/jellaharshith/SWIFT --skill hunt-http-smuggling
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-http-smuggling
Source: https://github.com/jellaharshith/SWIFT/tree/main/swift/skills/cbh/skills/hunt-http-smuggling
Command: npx skills add https://github.com/jellaharshith/SWIFT --skill hunt-http-smuggling

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you hunt for HTTP request smuggling by identifying parser disagreements between a front-end proxy and a back-end server so you can confirm and validate the cross-client impact.

Core Features & Use Cases

  • Protocol-vector coverage: Focuses on CL.TE, TE.CL, H2.CL, and H2.TE smuggling paths, including modern HTTP/2 downgrade scenarios.
  • Hunting workflow and confirmation: Provides detection approaches (e.g., Burp HTTP Request Smuggler, smuggler tooling, and timing-based confirmation) and validation ideas that distinguish real smuggling effects from self-induced delays.
  • Operator targeting guidance: Includes a target-suitability matrix and fingerprinting guidance to prioritize realistic CDN + origin and load balancer/WAF bypass opportunities.
  • Chain linkage for real-world triage: References common escalation chains such as cache poisoning, auth bypass, session attachment/credential theft, and reflected XSS at the victim queue level.

Quick Start

Use the hunt-http-smuggling skill to identify whether your target’s front-end/origin stack is vulnerable to CL.TE, TE.CL, or HTTP/2 downgrade smuggling, then confirm exploitability using a timing-based cross-request technique.

Frequently Asked Questions about hunt-http-smuggling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is HTTP request smuggling and how does front-end proxy parsing cause it?

HTTP request smuggling occurs when a front-end proxy and back-end server disagree on request boundary parsing, allowing attackers to inject smuggled requests that bypass security controls and affect other users.

How do I detect CL.TE and TE.CL smuggling vulnerabilities in a CDN and origin setup?

You can detect CL.TE and TE.CL smuggling by fingerprinting the front-end proxy for RFC strictness, then using Burp HTTP Request Smuggler or smuggler tooling to probe parsing inconsistencies between the CDN and origin.

Can I test HTTP/2 downgrade smuggling vulnerabilities targeting load balancers and WAFs?

Yes, you can test HTTP/2 downgrade smuggling by probing H2.CL and H2.TE vectors where HTTP/2-to-HTTP/1.1 downgrade behavior diverges across load balancer, WAF-protected, or proxy-chained deployments.

How do I validate HTTP request smuggling impact without false positives from self-induced delays?

Validate HTTP request smuggling impact using cross-client confirmation via timing or cache and auth effect validation, ensuring you observe real smuggling effects on another client rather than self-induced delays.

What real-world escalation chains can I achieve through HTTP request smuggling?

HTTP request smuggling enables escalation chains including cache poisoning, auth bypass, session attachment or credential theft, and reflected XSS at the victim queue level by injecting malicious requests into the back-end queue.