Skip to main content
CVE-2025-55181VulnerabilityPublished

Sending an HTTP request/response body with greater than 2^31 bytes triggers an infinite loop in

Source GCVE Database

0
Compare
Authoritative record:CVE-2025-55181· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium.

Data as of 22 Nov 2026, 02:57 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Meta)CVSS 3.15.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubfacebook/proxygenpkg:github/facebook/proxygenOther threatsAffected
  • =2025.08.25.00
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, limit or block HTTP request/response bodies larger than 2^31 bytes to prevent triggering the infinite loop and memory exhaustion.

Description

A vulnerability exists in proxygen::coro::HTTPQuicCoroSession where sending an HTTP request or response body larger than 2^31 bytes causes an infinite loop. This loop blocks the event loop and continuously appends data to a vector, leading to unbounded memory growth and eventual process memory exhaustion.

References

Community reviews

Loading reviews…