Loading vulnerability…
CVE-2026-25749 is a heap buffer overflow in Vim's help-file tag resolution logic before upstream version 9.1.2132. The get_tagfname() function copies the user-controlled 'helpfile' option into a fixed-size heap buffer of MAXPATHL + 1 bytes, typically 4097 bytes, using STRCPY() without bounds checking. An oversized option value can overflow the allocation when help-file tags are resolved. Successful exploitation can permit arbitrary code execution.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
29 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Vim's get_tagfname() function copies the user-controlled helpfile option into a fixed-size heap buffer using STRCPY() without bounds checking. The advisory identifies affected Vim packages on AlmaLinux 9.2 and recommends updating them.
A Vim vulnerability referenced by the advisory; no technical details are supplied.
Vim vulnerability referenced by the TuxCare security update.
A heap buffer overflow in Vim tag-file resolution caused by an unchecked copy of the user-controlled helpfile option; fixed in Vim 9.1.2132.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.