Facebook proxygen up to 2025.12.01.00 Body proxygen::coro iteration
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in Facebook proxygen up to 2025.12.01.00. Affected by this issue is the function proxygen::coro of the component Body Handler. Such manipulation leads to iteration.
This vulnerability is listed as CVE-2025-55181. The attack may be performed from remote. There is no available exploit.
It is advisable to implement a patch to correct this issue.
Details
A vulnerability was found in Facebook proxygen up to 2025.12.01.00 and classified as problematic. Affected by this issue is the function proxygen::coro of the component Body Handler. The manipulation with an unknown input leads to a iteration vulnerability. Using CWE to declare the problem leads to CWE-834. The product performs an iteration or loop without sufficiently limiting the number of times that the loop is executed. Impacted is availability. CVE summarizes:
Sending an HTTP request/response body with greater than 2^31 bytes triggers an infinite loop in proxygen::coro::HTTPQuicCoroSession which blocks the backing event loop and unconditionally appends data to a std::vector per-loop iteration. This issue leads to unbounded memory growth and eventually causes the process to run out of memory.
The advisory is shared for download at facebook.com. This vulnerability is handled as CVE-2025-55181 since 08/08/2025. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1499.
Applying the patch 17689399ef99b7c3d3a8b2b768b1dba1a4b72f8f is able to eliminate this problem. The bugfix is ready for download at github.com.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-200372). Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.2
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.3
CNA Vector (Meta): 🔒
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: IterationCWE: CWE-834 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
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: 17689399ef99b7c3d3a8b2b768b1dba1a4b72f8f
Timeline
08/08/2025 CVE reserved12/03/2025 Advisory disclosed
12/03/2025 VulDB entry created
12/03/2025 VulDB entry last update
Sources
Product: github.comAdvisory: facebook.com
Status: Confirmed
CVE: CVE-2025-55181 (🔒)
GCVE (CVE): GCVE-0-2025-55181
GCVE (VulDB): GCVE-100-334148
EUVD: 🔒
Entry
Created: 12/03/2025 07:51Updated: 12/03/2025 10:17
Changes: 12/03/2025 07:51 (67), 12/03/2025 10:17 (1)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.