Application crash via invalid fragmented NAL state
Published Feb 19, 2026 · Updated Feb 19, 2026
Heap buffer underflow in Teluu pjmedia-video before 2.17 allows local users to crash H.264-sending applications via malformed bitstreams. In pjmedia_h264_packetize, a continuation-fragment path subtracts the configured MTU from nal_start and dereferences the resulting pointer without verifying that a preceding FU-A fragment exists. The path requires H.264 packetization other than single NAL, and the reported consequence is unexpected application termination.
Summary
What happened
Heap buffer underflow in Teluu pjmedia-video before 2.17 allows local users to crash H.264-sending applications via malformed bitstreams. In pjmedia_h264_packetize, a continuation-fragment path subtracts the configured MTU from nal_start and dereferences the resulting pointer without verifying that a preceding FU-A fragment exists. The path requires H.264 packetization other than single NAL, and the reported consequence is unexpected application termination.
The record
- CVE
- CVE-2026-26203
- Published
- Feb 19, 2026
- Updated
- Feb 19, 2026
- Vendor
- PJSIP
- Product
- pjmedia-video
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 19, 2026CVE publishedPublication date reported by the CVE source.
- Feb 19, 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=< 2.17
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