CVE-2026-57164: PJSIP heap buffer overflow in HTTP client

CVE-2026-57164 · Severity: medium · CVSS 5.9 · Published 2026-09-04

PJSIP is a multimedia communication library used by many applications to handle audio and video over the internet. A defect in its HTTP client can cause a memory corruption flaw when downloading large files from a web server. An attacker posing as a malicious web server could craft responses to crash applications or potentially execute code, affecting availability and security of systems relying on this library.

Technologies: PJSIP Pjproject, Teluu Pjsip. Vendors: PJSIP, Teluu.

Quick answers

Is CVE-2026-57164 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-57164 being exploited in the wild.
How severe is CVE-2026-57164?
Medium severity, with a CVSS score of 5.9, published 4 September 2026.
Which products and versions are affected?
PJSIP Pjproject 2.17 or lower.
Is there a fix for CVE-2026-57164?
A patch was published on 2026-09-04: patch available in commit 8d5956a Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-57164 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-57164?
Check whether you run PJSIP Pjproject or Teluu Pjsip at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A heap buffer overflow exists in the PJLIB-UTIL HTTP client (http_client.c) due to incorrect size calculation when buffering HTTP response bodies. The vulnerability occurs when an application receives the entire response body in a completion callback without using incremental on_data_read callbacks. When the server sends a body larger than twice the initially allocated buffer size (based on a potentially attacker-controlled Content-Length header), a single doubling of the buffer is insufficient, causing response data to be written past the end of the heap allocation. The flaw requires a network-reachable HTTP server; applications using incremental response streaming or connecting only to trusted servers are unaffected. Impact ranges from denial of service (application termination) to memory corruption. The patch is available in commit 8d5956a, which implements repeated buffer doubling until the buffer is large enough.

Affected products

  • PJSIP pjproject 2.17 or lower

Timeline

  • 2026-06-17: disclosed
  • 2026-09-04: patched: patch available in commit 8d5956a

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.