Loading vulnerability…
CVE-2026-34982 is a modeline sandbox bypass in Vim versions earlier than 9.2.0276. The complete, guitabtooltip, and printheader options lack the P_MLE flag, permitting modeline-based security checks to be bypassed. In addition, mapset() lacks a check_secure() call and can be abused from sandboxed expressions. Opening a crafted file can cause Vim to execute arbitrary operating-system commands.
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.
nomodeline.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.
17 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Vim vulnerability referenced by the advisory; no technical details are supplied.
An Important-severity locally exploitable vulnerability addressed by a Rocky Linux 9.6 TuxCare live-security patch notice. The supplied CVSS v3 vector indicates local attack access, no privileges required, user interaction required, scope changed, and high confidentiality and integrity impact, with no availability impact.
Vim vulnerability referenced by the TuxCare security update.
A vulnerability referenced by the Nutanix AHV Nessus plugin; individual technical details are not provided.
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.