Buffer overflow in pjlib scanner and pjmedia

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

• pjsip pjsipbefore 2.13

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

• pjsip pjproject

  • < 2.13affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Other highest-scoring records for the same primary product.

• CVE-2022-24786Potential out-of-bound read/write in PJSIP
  40Plan
• CVE-2022-23547Heap buffer overflow in pjproject when decoding STUN message
  39Monitor
• CVE-2026-40614PJSIP: Heap buffer overflow in Opus codec decoding
  34Monitor
• CVE-2026-29068PJSIP: Stack buffer overflow in Opus codec parser
  34Monitor
• CVE-2026-28799PJSIP: Heap use-after-free in PJSIP presence subscription termination handler
  34Monitor
• CVE-2026-32945PJSIP is vulnerable to Heap-based Buffer Overflow through DNS parser
  33Monitor

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Root cause

When data is copied, the source length is not compared with the size of the destination buffer. Excess data overwrites adjacent memory.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

1char buf[256];2memcpy(buf, pkt->data, pkt->len);

1char buf[256];2if (pkt->len > sizeof(buf)) {3  return -EINVAL;4}5memcpy(buf, pkt->data, pkt->len);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.