Skip to main content
CVE-2026-121737VulnerabilityPublished

When a remote, unauthenticated HTTP/1.1 client pipelined the start of a second request and then stopped reading

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-121737· High

Not known to be exploited : upgrade to v2026.11.09.00 soon.

Data as of 11 Nov 2026, 20:03 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in v2026.11.09.00, 2026.11.09.00

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Nov 2026

  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 11 Nov 2026.

What to do

Upgrade proxygen to v2026.11.09.00; meta/proxygen to 2026.11.09.00.

Affected software

ProductAffectedFixed in
FacebookproxygenAffected
  • <2026.11.09.00
Fixed in
  • v2026.11.09.00
GitHubmeta/proxygenpkg:github/meta/proxygenOther threatsAffected
  • <2026.11.09.00
Fixed in
  • 2026.11.09.00

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

AI-suggested

A fix is available in proxygen version v2026.11.09.00. Users should upgrade to this version or later to remediate the vulnerability.

Description

A vulnerability in proxygen prior to version v2026.11.09.00 allows a remote, unauthenticated HTTP/1.1 client to cause a server crash by pipelining the start of a second request and then stopping reading. This leads to the server freeing a pipelined stream incorrectly during a write timeout, potentially causing denial of service and possible memory corruption.

References

Community reviews

Loading reviews…