Quick answers
- Is CVE-2026-77396 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-77396 being exploited in the wild.
- How severe is CVE-2026-77396?
- Informational severity, published 18 September 2026.
- Which products and versions are affected?
- PJSIP 2.17 and earlier.
- Is there a fix for CVE-2026-77396?
- A patch was published on 2026-07-13: Fix committed to master branch (7ecc658) Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-77396 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-77396?
- Check whether you run PJSIP at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The AVI parser uses a chunk length field from the input file to determine how many bytes to copy into the frame buffer, without validating it against the buffer capacity derived from declared media dimensions. This heap-based buffer overflow (CWE-122, CWE-787) occurs when reading frames from a crafted AVI file. The only guard is an assertion, which is disabled in release builds; a fix clamping reads to buffer capacity and removing assertion reliance has been committed.
Affected products
- PJSIP PJSIP 2.17 and earlier
Timeline
- 2026-07-13: disclosed: GHSA-6p2p-5wf8-h5hr published
- 2026-09-18: disclosed: CVE-2026-77396 published
- 2026-07-13: patched: Fix committed to master branch (7ecc658)