CVE-2026-40614 | pjsip pjproject up to 2.16 codec_parse dec_frame[].buf heap-based overflow

VDB-358555 · CVE-2026-40614 · GCVE-0-2026-40614 PJSIP PJPROJECT UP TO 2.16 CODEC_PARSE DEC_FRAME[].BUF HEAP-BASED OVERFLOW HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 5.3 $0-$5k 1.74+ Summaryinfo A vulnerability, which was classified as critical, has been found in pjsip pjproject up to 2.16. Affected is the function codec_parse. This manipulation of the argument dec_frame[].buf causes heap-based overflow. This vulnerability is registered as CVE-2026-40614. The attack needs to be launched locally. No exploit is available. Detailsinfo A vulnerability has been found in pjsip pjproject up to 2.16 and classified as critical. Affected by this vulnerability is the function codec_parse. The manipulation of the argument dec_frame[].buf with an unknown input leads to a heap-based overflow vulnerability. The CWE definition for the vulnerability is CWE-122. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is: PJSIP is a free and open source multimedia communication library written in C. In 2.16 and earlier, there is a buffer overflow when decoding Opus audio frames due to insufficient buffer size validation in the Opus codec decode path. The FEC decode buffers (dec_frame[].buf) were allocated based on a PCM-derived formula: (sample_rate/1000) * 60 * channel_cnt * 2. At 8 kHz mono this yields only 960 bytes, but codec_parse() can output encoded frames up to MAX_ENCODED_PACKET_SIZE (1280) bytes via opus_repacketizer_out_range(). The three pj_memcpy() calls in codec_decode() copied input->size bytes without bounds checking, causing a heap buffer overflow. It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-40614 since 04/14/2026. The exploitation appears to be easy. Attacking locally is a requirement. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/21/2026). There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product. Productinfo Type Project Management Software Vendor pjsip Name pjproject Version 2.0 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 2.10 2.11 2.12 2.13 2.14 2.15 2.16 License open-source Website Product: https://github.com/pjsip/pjproject/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA CVSS-B Score: 🔒 CNA CVSS-BT Score: 🔒 CNA Vector: 🔒 CVSSv3info VulDB Meta Base Score: 5.3 VulDB Meta Temp Score: 5.3 VulDB Base Score: 5.3 VulDB Temp Score: 5.3 VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Heap-based overflow CWE: CWE-122 / CWE-119 CAPEC: 🔒 ATT&CK: 🔒 Physical: Partially Local: Yes Remote: Partially Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: no mitigation known Status: 🔍 0-Day Time: 🔒 Timelineinfo 04/14/2026 CVE reserved 04/21/2026 +7 days Advisory disclosed 04/21/2026 +0 days VulDB entry created 04/21/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: github.com Status: Confirmed CVE: CVE-2026-40614 (🔒) GCVE (CVE): GCVE-0-2026-40614 GCVE (VulDB): GCVE-100-358555 Entryinfo Created: 04/21/2026 20:57 Changes: 04/21/2026 20:57 (67) Complete: 🔍 Cache ID: 99:C21:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸