Remote memory corruption via unchecked NAL size read
Published Feb 20, 2026 · Updated Feb 20, 2026
Heap-based buffer overflow in Teluu PJPROJECT 2.16 and earlier allows remote attackers to corrupt memory via malformed H.264 SRTP packets. In pjmedia_h264_unpacketize(), the H.264 unpacketizer reads a two-byte NAL unit size without first ensuring that two payload bytes remain. Only applications built with video support that receive H.264 media reach this path; successful exploitation can compromise or interrupt the process.
Summary
What happened
Heap-based buffer overflow in Teluu PJPROJECT 2.16 and earlier allows remote attackers to corrupt memory via malformed H.264 SRTP packets. In pjmedia_h264_unpacketize(), the H.264 unpacketizer reads a two-byte NAL unit size without first ensuring that two payload bytes remain. Only applications built with video support that receive H.264 media reach this path; successful exploitation can compromise or interrupt the process.
The record
- CVE
- CVE-2026-26967
- Published
- Feb 20, 2026
- Updated
- Feb 20, 2026
- Vendor
- PJSIP
- Product
- PJPROJECT
- Classifications
- CWE-122
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 20, 2026CVE publishedPublication date reported by the CVE source.
- Feb 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< f821c214e52b11bae11e4cd3c7f0864538fb5491
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo