---
id: "GHSA-vpp8-g58w-m8mp"
kind: "vulnerability"
aliases: ["GHSA-vpp8-g58w-m8mp"]
title: "Twisted: Unauthenticated Remote Denial of Service in the Twisted HTTP/2 Server via Rapid Stream Reset"
severity: "high"
cvss: 7.5
epss: null
exploited: false
status: "open"
category: "package"
products: [{"name": "Twisted", "fixed": ["26.10.0rc1"], "affected": "<= 26.4.0", "ecosystem": "pypi"}]
ecosystems: ["pypi"]
tags: ["cwe-400", "cwe-770", "http2", "package", "python", "self-hosted", "twisted"]
not_affected_if: ["http2-terminated-at-proxy", "no-http2-server"]
published_at: "2026-10-29T16:41:06+00:00"
first_seen_at: "2026-10-29T16:44:11+00:00"
updated_at: "2026-10-29T16:46:01+00:00"
sources: [{"source": "ghsa", "url": "https://github.com/advisories/GHSA-vpp8-g58w-m8mp", "first_seen_at": "2026-10-29T16:44:11+00:00"}]
---

# Twisted: Unauthenticated Remote Denial of Service in the Twisted HTTP/2 Server via Rapid Stream Reset

Twisted's HTTP/2 server renders each request whose stream is reset right after the headers, so one connection can force unbounded request processing. An unauthenticated remote client can exhaust server CPU, causing denial of service with no data access or code execution.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- pypi:Twisted affected <= 26.4.0 fixed 26.10.0rc1

## How to check

- Check the installed Twisted version with `pip show Twisted` or `python -c "import twisted; print(twisted.__version__)"`, and compare it to the affected range `<= 26.4.0`.
- Look for HTTP/2 enabled on a Twisted `twisted.web` server, since the flaw is in the `_http2.py` path.

## Fix

- Twisted: move to `26.10.0rc1` or later (fixed version per the sources).

## Timeline

- 2026-10-29T16:44:11+00:00 ghsa https://github.com/advisories/GHSA-vpp8-g58w-m8mp

## Documents

- [advisory] Maintainer's advisory: api.github.com https://api.github.com/repos/twisted/twisted/security-advisories/GHSA-vpp8-g58w-m8mp
- [advisory] Maintainer's advisory: github.com https://github.com/twisted/twisted/security/advisories/GHSA-vpp8-g58w-m8mp
- [fix] Patch: github.com https://github.com/twisted/twisted/pull/12749
- [fix] Patch: github.com https://github.com/twisted/twisted/commit/498939422b69d5a75c4b8f81fa7926423dac534d
- [fix] Release: github.com https://github.com/twisted/twisted/releases/tag/twisted-26.10.0rc1

## From the sources

## Summary

An uncontrolled-resource-consumption vulnerability (CWE-400) in the Twisted HTTP/2 server lets any unauthenticated remote client exhaust server CPU over a single connection. A client that sends a request header block with `END_STREAM` and then immediately resets the stream makes the server route and render the request before it processes the reset. Reset streams are freed and never count against the concurrent-stream limit, and no reset-rate limiter exists, so the pattern can be repeated at line rate on one connection. This is the HTTP/2 Rapid Reset class, CVE-2023-44487.

## Details

For one received segment the h2 events are processed in order in `H2Connection.dataReceived`. A `HEADERS(END_STREAM)` followed by `RST_STREAM` yields `RequestReceived`, `StreamEnded`, then `StreamReset`, so the request is dispatched and rendered on stream end before the reset is handled:

```python
# src/twisted/web/_http2.py  (H2Connection.dataReceived)
for event in events:
    if isinstance(event, h2.events.RequestReceived):
        self._requestReceived(event)     # allocate the request
    elif isinstance(event, h2.events.StreamEnded):
        self._requestEnded(event)        # -> requestComplete -> render() synchronously
    elif isinstance(event, h2.events.StreamReset):
        self._requestAborted(event)      # processed last, frees the stream
```

`_requestAborted` frees the reset stream, so it never occupies the 100-stream concurrency budget, and nothing in `_http2.py` counts or throttles opened-and-reset streams. The 2019 flood fix (GHSA-32gv) bounds outbound control-frame buffering only and does not apply to this path.

Affected product: Twisted, `twisted.web` HTTP/2 server
Affected versions: confirmed against 26.4.0

## PoC

On any Twisted HTTP/2 endpoint, open one connection and, in a tight loop, send a `HEADERS` frame with `END_STREAM` on a fresh stream identifier immediately followed by a `RST_STREAM` for that stream, at line rate. No credentials are required. The server renders each request on stream end before the reset frees the stream, and a freed stream never counts toward the concurrent-stream limit, so the loop is never throttled.

Because every cancelled stream is still dispatched in full and reset streams do not accumulate, the connection is never throttled or closed, so the forced work grows with the number of pairs sent. Sustained on one connection this saturates a CPU core under only a trickle of traffic, whereas a client that instead leaves its streams open is closed once it reaches the concurrent-stream limit.

## Impact

This is an unauthenticated remote denial of service (CWE-400, CWE-770) by CPU exhaustion. One connection forces unbounded request rendering at a few frames per cancelled request, bypassing the concurrent-stream limit. It is the HTTP/2 Rapid Reset class (CVE-2023-44487), not covered by the earlier Twisted flood fix, with no confidentiality or integrity impact and no code execution.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_