CVE and update status of the FreeBSD ports tree3,296 unaddressed CVEs in 671 portsAll times are CET
CVE details

CVE-2026-57160

PJSIP is a free and open source multimedia communication library written in C. Prior to commit d6a0e7f, a buffer overflow can occur in pjsip_generic_array_hdr_print() in pjsip/src/pjsip/sip_msg.c, the function that serializes generic array headers (such as Allow, Require, Supported, and Unsupported). Under certain output-buffer boundary conditions the function can write one byte past the end of the buffer. This is reachable mainly in applications that parse and re-serialize incoming SIP requests — for example a proxy, SBC, or B2BUA — where a remote peer can influence the serialized message. The out-of-bounds write is a single fixed byte; code execution and information disclosure are not demonstrated, and in typical pool-based allocations the byte falls within allocation slack. This issue has been patched via commit d6a0e7f.

Score
6.9 medium
Published
2026-09-04
Links
NVD · cve.org · Report wrong data

Matched ports (1)

PortPackageVersionStatusMaintainer
net/pjsippjsip2.14.1unaddressedoliver.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 d6a0e7f, a buffer overflow can occur in
	pjsip_generic_array_hdr_print() in pjsip/src/pjsip/sip_msg.c, the
	function that serializes generic array headers (such as Allow,
	Require, Supported, and Unsupported). Under certain output-buffer
	boundary conditions the function can write one byte past the end of
	the buffer. This is reachable mainly in applications that parse and
	re-serialize incoming SIP requests — for example a proxy, SBC, or
	B2BUA — where a remote peer can influence the serialized message.
	The out-of-bounds write is a single fixed byte; code execution and
	information disclosure are not demonstrated, and in typical pool-based
	allocations the byte falls within allocation slack. This issue has
	been patched via commit d6a0e7f.</p>
      </body>
    </description>
    <references>
      <cvename>CVE-2026-57160</cvename>
      <url>https://nvd.nist.gov/vuln/detail/CVE-2026-57160</url>
    </references>
    <dates>
      <discovery>2026-09-04</discovery>
      <entry>2026-10-26</entry>
    </dates>
  </vuln>