te0-request-smuggling

Detect TE.0 HTTP request smuggling in reverse proxy and backend architectures.

11|1|Updated May 4, 2026
One-click install
npx skills add https://github.com/dreadnode/capabilities --skill te0-request-smuggling
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: te0-request-smuggling
Source: https://github.com/dreadnode/capabilities/tree/main/capabilities/web-security/skills/te0-request-smuggling
Command: npx skills add https://github.com/dreadnode/capabilities --skill te0-request-smuggling

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standard HTTP request smuggling probes for CL.TE and TE.CL variants fail to detect TE.0 smuggling, a vulnerability that occurs when a front-end reverse proxy processes Transfer-Encoding chunked requests but the back-end server entirely ignores the Transfer-Encoding header, leaving the attack undetected by conventional testing methods.

Core Features & Use Cases

  • Specialized TE.0 Probe: Includes a crafted HTTP request designed to trigger TE.0 smuggling behavior in vulnerable reverse proxy and backend architectures.
  • Exploitation Indicators: Provides clear signs of successful smuggling, including response poisoning, unexpected redirects to attacker-controlled domains, and cross-user session data leakage.
  • Common Target Coverage: Targets prevalent vulnerable configurations including Google Cloud-hosted applications, AWS ALB deployments, and misconfigured nginx backends.
  • Use Case: Use this skill during web application penetration tests to identify high-severity HTTP request smuggling vulnerabilities that evade standard detection tools.

Quick Start

Use the te0-request-smuggling skill to test a reverse proxy and backend web application for TE.0 request smuggling vulnerabilities after standard CL.TE and TE.CL probes have returned no findings.

Frequently Asked Questions about te0-request-smuggling

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

FAQPage Schema
What is TE.0 HTTP request smuggling and how does it differ from standard CL.TE or TE.CL smuggling?▼

TE.0 HTTP request smuggling occurs when a front-end reverse proxy processes Transfer-Encoding chunked requests but the back-end server entirely ignores the Transfer-Encoding header, making it undetectable by standard CL.TE and TE.CL probes.

How do I detect HTTP request smuggling on AWS ALB or Google Cloud when standard probes fail?▼

To detect HTTP request smuggling on AWS ALB or Google Cloud when standard probes fail, use a specialized TE.0 probe designed to trigger smuggling behavior in architectures where the back-end ignores the Transfer-Encoding header.

What are the exploitation indicators of a successful TE.0 request smuggling attack?▼

Exploitation indicators of a successful TE.0 request smuggling attack include response poisoning, unexpected redirects to attacker-controlled domains, and cross-user session data leakage caused by smuggled HTTP requests.

Does this TE.0 request smuggling probe work against misconfigured nginx backends?▼

Yes, this TE.0 request smuggling probe works against misconfigured nginx backends, as well as Google Cloud-hosted applications and AWS ALB deployments that process chunked requests at the front-end but ignore them at the back-end.

When should I use a TE.0 smuggling probe instead of standard HTTP request smuggling detection tools?▼

Use a TE.0 smuggling probe instead of standard HTTP request smuggling detection tools during authorized penetration tests after standard CL.TE and TE.CL probes return no findings but a vulnerability is still suspected.