CVE-2026-57161
PJSIP is a free and open source multimedia communication library written in C. Prior to commit acc03b5, a stack buffer overflow exists in PJSUA when processing Service-Route headers in a registration response (update_service_route() in pjsua_acc.c). This affects applications that register using the PJSUA/PJSUA2 account API (the default registration path). The Service-Route URIs from a 2xx response to REGISTER are stored into a fixed-size array without bounding the number of headers; a registrar that returns an excessive number of Service-Route headers can write past the end of the array on the stack. The values written are internal pointers rather than arbitrary data, so the most likely impact is unexpected application termination (denial of service), though memory corruption cannot be excluded. The malicious response may come from a compromised or malicious registrar, or — over unprotected transports — a spoofed response. This issue has been patched via commit acc03b5.
- Score
- 8.8 high
- Published
- 2026-09-04
- Links
- NVD · cve.org · Report wrong data
Matched ports (1)
| Port | Package | Version | Status | Maintainer |
|---|---|---|---|---|
| net/pjsip | pjsip | 2.14.1 | unaddressed | oliver.epper@gmail.com |
Template for a VuXML entry
Range taken from the CVE record, check it before committing. make newentry in security/vuxml creates the vid.
<vuln vid="FIXME (make newentry)">
<topic>FIXME -- FIXME</topic>
<affects>
<package>
<name>pjsip</name>
<range><lt>FIXME</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>PJSIP is a free and open source multimedia communication library
written in C. Prior to commit acc03b5, a stack buffer overflow exists
in PJSUA when processing Service-Route headers in a registration
response (update_service_route() in pjsua_acc.c). This affects
applications that register using the PJSUA/PJSUA2 account API (the
default registration path). The Service-Route URIs from a 2xx response
to REGISTER are stored into a fixed-size array without bounding the
number of headers; a registrar that returns an excessive number of
Service-Route headers can write past the end of the array on the
stack. The values written are internal pointers rather than arbitrary
data, so the most likely impact is unexpected application termination
(denial of service), though memory corruption cannot be excluded. The
malicious response may come from a compromised or malicious registrar,
or — over unprotected transports — a spoofed response. This issue
has been patched via commit acc03b5.</p>
</body>
</description>
<references>
<cvename>CVE-2026-57161</cvename>
<url>https://nvd.nist.gov/vuln/detail/CVE-2026-57161</url>
</references>
<dates>
<discovery>2026-09-04</discovery>
<entry>2026-10-26</entry>
</dates>
</vuln>