Facebook Proxygen up to 2017.01.16.00/2026.07.20.00 Core HTTP Session Layer allocation of resources
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 3.51+ |
Summary
A vulnerability categorized as problematic has been discovered in Facebook Proxygen up to 2017.01.16.00/2026.07.20.00. This impacts an unknown function of the component Core HTTP Session Layer. Such manipulation leads to allocation of resources. This vulnerability is traded as CVE-2026-44909. The attack may be launched remotely. There is no exploit available.
Details
A vulnerability, which was classified as problematic, has been found in Facebook Proxygen up to 2017.01.16.00/2026.07.20.00. Affected by this issue is an unknown functionality of the component Core HTTP Session Layer. The manipulation with an unknown input leads to a allocation of resources vulnerability. Using CWE to declare the problem leads to CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. Impacted is availability. CVE summarizes:
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.
The advisory is available at github.com. This vulnerability is handled as CVE-2026-44909 since 05/08/2026. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 07/23/2026). This vulnerability is assigned to T1499 by the MITRE ATT&CK project.
Applying the patch f28742f21f7022c261b7620d4e6b20d82b6cff72 is able to eliminate this problem.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
- 2017.01.0
- 2017.01.1
- 2017.01.2
- 2017.01.3
- 2017.01.4
- 2017.01.5
- 2017.01.6
- 2017.01.7
- 2017.01.8
- 2017.01.9
- 2017.01.10
- 2017.01.11
- 2017.01.12
- 2017.01.13
- 2017.01.14
- 2017.01.15
- 2017.01.16.00
- 2026.07.0
- 2026.07.1
- 2026.07.2
- 2026.07.3
- 2026.07.4
- 2026.07.5
- 2026.07.6
- 2026.07.7
- 2026.07.8
- 2026.07.9
- 2026.07.10
- 2026.07.11
- 2026.07.12
- 2026.07.13
- 2026.07.14
- 2026.07.15
- 2026.07.16
- 2026.07.17
- 2026.07.18
- 2026.07.19
- 2026.07.20.00
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Allocation of resourcesCWE: CWE-770 / CWE-400 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔒
Patch: f28742f21f7022c261b7620d4e6b20d82b6cff72
Timeline
05/08/2026 CVE reserved07/23/2026 Advisory disclosed
07/23/2026 VulDB entry created
07/23/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-44909 (🔒)
GCVE (CVE): GCVE-0-2026-44909
GCVE (VulDB): GCVE-100-382754
Entry
Created: 07/23/2026 19:00Changes: 07/23/2026 19:00 (55)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.