Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Fri, 24 Jul 2026 00:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Facebook
Facebook proxygen |
|
| Vendors & Products |
Facebook
Facebook proxygen |
Thu, 23 Jul 2026 21:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Proxygen lacked a generalized slow-consumer detection mechanism in its core HTTP session layer. A remote, unauthenticated attacker could exploit HTTP/2 flow-control by setting SETTINGS_INITIAL_WINDOW_SIZE to 0 or withholding WINDOW_UPDATE frames, causing the server to buffer complete response bodies in memory indefinitely for stalled streams. By opening many simultaneous streams requesting large resources while preventing the server from transmitting responses, an attacker could induce unbounded memory growth leading to service degradation, resource exhaustion, or denial of service. Versions v2017.01.16.00 through v2026.07.20.00 are affected. | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: Meta
Published:
Updated: 2026-07-23T19:07:28.874Z
Reserved: 2026-05-08T02:33:35.450Z
Link: CVE-2026-44909
Updated: 2026-07-23T19:07:24.780Z
No data.
No data.
OpenCVE Enrichment
Updated: 2026-07-24T00:00:05Z
No weakness.