Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Thu, 23 Apr 2026 16:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Pjsip pjsip
|
|
| CPEs | cpe:2.3:a:pjsip:pjsip:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Pjsip pjsip
|
|
| Metrics |
cvssV3_1
|
Wed, 22 Apr 2026 14:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 22 Apr 2026 03:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Pjsip
Pjsip pjproject |
|
| Vendors & Products |
Pjsip
Pjsip pjproject |
Wed, 22 Apr 2026 00:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | PJSIP: Heap buffer overflow in Opus codec decoding | |
| Weaknesses | CWE-122 | |
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-04-22T13:33:23.816Z
Reserved: 2026-04-14T14:07:59.642Z
Link: CVE-2026-40614
Updated: 2026-04-22T13:33:18.188Z
Status : Analyzed
Published: 2026-04-21T19:16:17.880
Modified: 2026-04-23T16:09:54.393
Link: CVE-2026-40614
No data.
OpenCVE Enrichment
Updated: 2026-04-22T05:45:09Z