Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| proxygen | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Proxygen |
|
No CVSS v4.0
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.193% probability within 30 days)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Server Crash and Possible Memory Corruption via Pipelined HTTP/1.1 Requests in Facebook Proxygen | |
| Weaknesses | CWE-119 CWE-416 |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Facebook
Facebook proxygen |
|
| Vendors & Products |
Facebook
Facebook proxygen |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Server Crash and Possible Memory Corruption via Pipelined HTTP/1.1 Requests in Facebook Proxygen | |
| Weaknesses | CWE-119 CWE-416 |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | When a remote, unauthenticated HTTP/1.1 client pipelined the start of a second request and then stopped reading, proxygen's coroutine-based HTTP session could free that pipelined stream while resetting the connection's streams on the resulting write timeout, then go on to use it. This can crash the server, leading to denial of service, and may allow memory corruption with further impact. This issue affects proxygen versions prior to v2026.11.09.00. | |
| References |
|
No weakness.