Process crash via unchecked realloc failure
Published Aug 4, 2026 · Updated Aug 4, 2026
A reported NULL pointer dereference in Vim 9.2.0389 and earlier allows local users to crash OpenVMS builds during filename processing. In src/os_vms.c, vms_fixfilename() assigns vim_realloc() directly to its static buffer and then uses that pointer in string-copy operations without checking for NULL. The claim requires an OpenVMS build, filename or path handling, and allocation failure; Ubuntu disputes the report as apparently AI-generated.
Summary
What happened
A reported NULL pointer dereference in Vim 9.2.0389 and earlier allows local users to crash OpenVMS builds during filename processing. In src/os_vms.c, vms_fixfilename() assigns vim_realloc() directly to its static buffer and then uses that pointer in string-copy operations without checking for NULL. The claim requires an OpenVMS build, filename or path handling, and allocation failure; Ubuntu disputes the report as apparently AI-generated.
The record
- CVE
- CVE-2026-51401
- Published
- Aug 4, 2026
- Updated
- Aug 4, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-94
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Aug 4, 2026CVE publishedPublication date reported by the CVE source.
- Aug 4, 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
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