Process crash via zero-length NAL parsing
Published Sep 24, 2026 · Updated Sep 24, 2026
NULL pointer dereference in libde265 commit 4d45a6b allows attackers to crash UBSan-instrumented processes via a zero-length NAL unit. The de265_push_NAL path can leave a NAL_unit with a NULL backing buffer, and NAL_unit::set_data passes that pointer to memcpy even when the copy length is zero. Triggering the documented termination requires a UBSan-instrumented build; public evidence does not establish behavior in ordinary builds or a network delivery path.
Summary
What happened
NULL pointer dereference in libde265 commit 4d45a6b allows attackers to crash UBSan-instrumented processes via a zero-length NAL unit. The de265_push_NAL path can leave a NAL_unit with a NULL backing buffer, and NAL_unit::set_data passes that pointer to memcpy even when the copy length is zero. Triggering the documented termination requires a UBSan-instrumented build; public evidence does not establish behavior in ordinary builds or a network delivery path.
The record
- CVE
- CVE-2026-88373
- Published
- Sep 24, 2026
- Updated
- Sep 24, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1499
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 24, 2026CVE publishedPublication date reported by the CVE source.
- Sep 24, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
No CVSS assessment is available in this record.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started