AI-Assisted "HTTP Terminator" Uncovers Novel HTTP Desync Techniques and Apache Traffic Server Zero-Day (CVE-2026-63078)

AI-Assisted "HTTP Terminator" Uncovers Novel HTTP Desync (TL-2026-1961), also tracked as HTTP Terminator Desync Research, is a high-severity software vulnerability, first published 2026-08-09. It has no confirmed attribution, affects Apache Software Foundation Apache Traffic Server, references 1 CVE (CVE-2026-63078), maps to 12 MITRE ATT&CK techniques (T1027, T1071.001, T1119), and is covered by 9 detection rules and 10 indicators of compromise.

Key facts for TL-2026-1961

Threat ID
TL-2026-1961
Also known as
HTTP Terminator Desync Research, Apache Traffic Server Desync Zero-Day
Severity
HIGH
Status
ACTIVE
Category
VULNERABILITY
First published
2026-08-09
Last reviewed
2026-08-09
Attribution confidence
LOW
Motivation
UNKNOWN
Target sectors
financial services, government administration, aviation, critical infrastructure, technology, cybersecurity vendors
Target regions
united states of america, Global
Detection rules
9
Indicators of compromise
10

Malware and tooling in AI-Assisted "HTTP Terminator" Uncovers Novel HTTP Desync

Malware and tooling: BeyondTrust, HTTP Request Smuggler, HTTP Terminator, Param Miner (protocol-ruler technique), Turbo Intruder (MCP interface update)

PortSwigger Director of Research James Kettle built HTTP Terminator, an AI-assisted research pipeline that ingested 138 HTTP/SMTP RFCs, fragmented them into ~15,000 micro-inspirations, and generated 30,000 candidate HTTP desynchronization vectors tested against 30,000 authorized bug-bounty sites. The system surfaced novel desync classes (dual-matching Content-Length, a dangling-byte response-queue-poisoning reliability trick, Shared-Parser Confusion, a Content-Type: multipart/byteranges trigger, status-line injection, and range cache poisoning) and, via human-guided follow-up, a zero-day desync flaw in Apache Traffic Server (CVE-2026-63078), since patched. Validation found roughly 700 vulnerable targets among the 30,000 tested, including a U.S. bank, a .gov site, an airport (via F5 BIG-IP), and Meta, Citrix NetScaler, and Microsoft Azure Application Gateway deployments.

How AI-Assisted "HTTP Terminator" Uncovers Novel HTTP Desync works

HTTP Terminator is an AI-assisted vulnerability-research pipeline built by PortSwigger Director of Research James Kettle, with collaborators Paolo 'sw33tLie' Arnolfo and Francesco 'Medusa' Mariani, and publicly released on GitHub (PortSwigger/http-terminator) under AGPL-3.0. The pipeline runs a four-stage cascade — Seeker (Python, uses Claude to extract candidate techniques from RFC text), Flamer (Java/Gradle, generates malformed HTTP test cases), Validator (a Burp Suite extension that tests generated requests against live, authorized targets), and Investigator (Python, uses Claude Code plus an MCP simulator and Burp Organizer to replicate and confirm findings) — conceptually described by PortSwigger as Ideation, Evaluation, Weaponization, and Cascade. The system ingested 138 HTTP and SMTP RFCs, fragmented them into roughly 15,000 one-to-three-sentence 'micro-inspiration' chunks (deliberately avoiding the words 'desync' and 'smuggling' to maximize novelty), and produced 30,000 unique candidate desync vectors after deduplication, each fragment yielding one to five candidate requests to limit context contamination. These vectors were validated against 30,000 real, authorized-scope bug-bounty targets.

The research produced several genuinely novel desync technique classes. Dual-matching Content-Length abuses servers that treat two identical, duplicated Content-Length headers as signaling a zero-length body, letting a second smuggled request ride through undetected (observed against an SSO endpoint and a Meta server). The dangling-byte technique deliberately leaves a smuggled request exactly one byte short so the back-end withholds its second response until a genuine victim request arrives — this was the only survivor of 16 reliability concepts evaluated for response-queue poisoning (RQP), eliminating the race conditions that normally make RQP unreliable. A Content-Type: multipart/byteranges trigger misapplies RFC 9112 §6.1 response-framing rules to a request, and alone affected 200+ sites including an American bank. Shared-Parser Confusion, a concept proposed by the AI system and then manually validated by Kettle, exploits servers that reuse the same parsing logic for both requests and responses, letting response-only directives (such as Set-Cookie handling) be triggered via crafted request headers. Two further techniques were documented: status-line injection, where an unsanitized protocol string is copied verbatim into a back-end response status line and breaks front-end response buffering (observed against a redacted bank), and range cache poisoning, where a manipulated range request causes an origin to return HTTP 200 instead of 206 Partial Content, causing a shared cache to store and later serve an incomplete response as the complete resource.

Human-guided follow-up on a malformed-request cascade led to a zero-day desync flaw in Apache Traffic Server, tracked as CVE-2026-63078. The trigger combines a DELETE request carrying a Content-Location header and Max-Forwards: 0 with a trailing, smuggled TRACE request; the flaw was confirmed when injected inline headers reappeared inside the server's response. The vendor patched the issue prior to PortSwigger's public disclosure. Notably, as of the article's 7 August 2026 publication no public CVE record existed for CVE-2026-63078 at CVE.org or NVD, and it is NOT among the 34 CVEs Apache Traffic Server addressed in its July 2026 9.2.15/10.1.4 security release (which covered unrelated use-after-free, HostDB memory-leak, and prefetch-plugin issues) — leaving the affected-version range for this specific desync flaw publicly undocumented at time of writing.

Beyond the single confirmed Apache CVE, deeper validation against the full 30,000-site pool found roughly 700 vulnerable targets spanning banking, government, security-product, and airport/transportation infrastructure. Named product exposures during testing included F5 BIG-IP (an airport target), Citrix NetScaler (a bank misconfiguration), Microsoft Azure Application Gateway (via an Early-Data header trigger), Akamai (in an Apache-proxy scenario), and BeyondTrust Secure Remote Access (a CONNECT-request flaw, which prompted BeyondTrust to inquire about the replication methodology). PortSwigger published the research as 'Can AI do novel security research? Meet the HTTP Terminator' on 5 August 2026 (updated 6 August), tied to Black Hat USA 2026 / DEF CON 34, and simultaneously open-sourced HTTP Terminator alongside updates to three existing Burp tools: HTTP Request Smuggler (new vectors plus contamination detection), Turbo Intruder (a new MCP interface for autonomous exploitation), and Param Miner (a new protocol-ruler header-analysis technique). The AI models struggled with autonomous exploitation of RQP without human guidance, producing false positives around HTTP pipelining, and a retrospective rediscovery benchmark found only a 30% success rate when a separate model (GPT-5.6 Sol) was given the same inspiration techniques — underscoring that human validation remained essential to turning the system's proposals into confirmed findings such as Shared-Parser Confusion and the Apache zero-day.

MITRE ATT&CK techniques used in TL-2026-1961

Defense Evasion

T1027 Obfuscated Files or Information

Command and Control

T1071.001 Web Protocols

Collection

T1119 Automated Collection

Initial Access

T1190 Exploit Public-Facing Application

Impact

T1499.004 Application or System Exploitation; T1565.002 Transmitted Data Manipulation

Credential Access

T1539 Steal Web Session Cookie; T1557 Adversary-in-the-Middle

Resource Development

T1587.004 Exploits; T1588.006 Vulnerabilities

Reconnaissance

T1592.002 Software; T1595.002 Vulnerability Scanning

Affected products and versions in AI-Assisted "HTTP Terminator" Uncovers Novel HTTP Desync

  • Apache Software Foundation — Apache Traffic Server
    Vulnerable versions: versions prior to the vendor's unpublished CVE-2026-63078 fix
    Fixed in: patched by vendor prior to 2026-08-05 disclosure; specific fixed release not publicly documented as of 2026-08-07
  • F5 — BIG-IP
    Vulnerable versions: deployment observed vulnerable to an RQP-based desync during HTTP Terminator validation (airport target); no CVE or version range published
  • Citrix — NetScaler
    Vulnerable versions: deployment observed with a desync-exposing misconfiguration during HTTP Terminator validation (bank target); no CVE or version range published
  • Microsoft — Azure Application Gateway
    Vulnerable versions: deployment observed vulnerable to an Early-Data header desync trigger during HTTP Terminator validation; no CVE or version range published

Remediation for AI-Assisted "HTTP Terminator" Uncovers Novel HTTP Desync

Patches

  • Apache Traffic Server: CVE-2026-63078 patched by the vendor prior to the 5 August 2026 public disclosure; specific fixed version not publicly documented as of 7 August 2026 and not included in the July 2026 9.2.15/10.1.4 security release.

Immediate actions

  • Patch Apache Traffic Server to the vendor's fixed release for CVE-2026-63078 as soon as version details are published.
  • Reject or normalize requests carrying duplicate/conflicting Content-Length headers at the front-end proxy rather than passing them through.
  • Reject request bodies declaring Content-Type: multipart/byteranges, since this content type is only valid on responses, never on requests.
  • Ensure front-end and back-end servers use a single, consistent HTTP parser/library version to close Shared-Parser Confusion and interpretation-mismatch gaps.

Workarounds

  • At the front-end proxy, drop connections whose requests contain two identical Content-Length headers instead of forwarding them.
  • Disable or restrict DELETE and TRACE method handling on Apache Traffic Server instances pending an official fix confirmation.

Longer-term hardening

  • Terminate client connections on HTTP/2 (or HTTP/1.1 with strict, RFC 9112-compliant parsing) between front-end and back-end hops to remove the parsing ambiguity desync attacks rely on.
  • Run PortSwigger's HTTP Request Smuggler, Turbo Intruder, and the open-sourced HTTP Terminator vectors against internet-facing proxy/CDN/WAF infrastructure as part of routine authorized testing.
  • Deploy connection-level anomaly monitoring for duplicate Content-Length headers, malformed status lines, and range requests returning 200 instead of 206.
  • Track vendor advisories for Apache Traffic Server, F5 BIG-IP, Citrix NetScaler, and Azure Application Gateway for desync-related patches following this disclosure.

CVEs associated with AI-Assisted "HTTP Terminator" Uncovers Novel HTTP Desync

CVE-2026-63078

Weaknesses (CWE) in AI-Assisted "HTTP Terminator" Uncovers Novel HTTP Desync

CWE-444, CWE-436

Timeline of AI-Assisted "HTTP Terminator" Uncovers Novel HTTP Desync

  • PortSwigger open-sources HTTP Terminator on GitHub and ships updated releases of HTTP Request Smuggler, Turbo Intruder (new MCP interface), and Param Miner (new protocol-ruler technique).
  • James Kettle discloses that HTTP Terminator's human-guided cascade uncovered a zero-day HTTP desync flaw in Apache Traffic Server (CVE-2026-63078), triggered by a DELETE request with a Content-Location header and a smuggled TRACE request, patched by the vendor prior to publication.
  • PortSwigger publishes 'Can AI do novel security research? Meet the HTTP Terminator,' detailing the AI-assisted desync-discovery methodology, the 700/30,000 vulnerable-site validation results, and CVE-2026-63078 as already patched.
  • PortSwigger updates the HTTP Terminator research write-up (14:59 UTC).
  • As of this date, no public CVE record for CVE-2026-63078 exists at CVE.org or NVD, and it is absent from Apache Traffic Server's July 2026 9.2.15/10.1.4 security release covering 34 unrelated CVEs, leaving the affected-version range for the desync flaw undocumented publicly.
  • The Hacker News publishes coverage of the HTTP Terminator research and the Apache Traffic Server zero-day.

Sources cited for AI-Assisted "HTTP Terminator" Uncovers Novel HTTP Desync

Threats related to AI-Assisted "HTTP Terminator" Uncovers Novel HTTP Desync

Detection coverage for TL-2026-1961

As of 2026-08-09, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-1961 across Splunk SPL, Microsoft KQL and Sigma, covering 10 indicator(s) of compromise. The whole corpus is readable without an account; a free account unlocks full detection query text in Splunk SPL, Microsoft KQL and Sigma; paid tiers add raw indicator values, correlation and the MCP server. Threadlinqs MCP server · View plans.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

[ 0 threats ] [ 0 det ] [ CRIT: 0 ] [ HIGH: 0 ]
// threat_feed
$ sort --newest
Showing all threats

Latest Threats