Read the docs

Insecure socket directory in Vim lets local users run expressions

Priority MEDIUM 45Published · Updated

Key facts

Attack vector
Local
Privileges required
None
User interaction
None
Attack complexity
High
Impact type
—
Confidentiality · integrity · availability
High · High · None
Fix status
Fixed

Attack profile from CVSS 3.1 · GHSA-p99j-mfjp-r4cg. Fix status from GitHub.

Summary

Vim before 9.2.1308 uses an existing socket directory in /tmp without checking its owner or permissions (CWE-283). A local user with an account on the same system can create that directory first, then connect to or replace the server socket of a Vim running the socketserver feature, and evaluate Vim expressions in the victim's Vim, which can lead to shell command execution.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

Description from the GitHub advisory

Insecure Socket Directory in Vim < 9.2.1308 ============================ Date: 08.11.2026 Severity: Medium CVE: *requested, not yet assigned* CWE: Unverified Ownership (CWE-283), Incorrect Default Permissions (CWE-276) ## Summary When using the socketserver backend of the clientserver feature, Vim places its socket in a per-user directory such as `/tmp/vim-<uid>`. An existing directory was used without checking its owner or permissions, and the socket was created with the user's umask. A local attacker can pre-create this directory and then connect to or replace the victim's server socket, which allows evaluating arbitrary Vim expressions in the victim's Vim. ## Description `socketserver_get_path()` creates the socket directory `$XDG_RUNTIME_DIR/vim` or `$TMPDIR/vim-<uid>` (`/tmp` if `$TMPDIR` is unset) using: if (vim_mkdir(buf, 0700) == -1 && errno != EEXIST) continue; If the directory already exists, it is used as-is. Since `/tmp` is world-writable, another user can create `/tmp/vim-<uid>` for the victim's uid beforehand, owned by the attacker and with permissive mode. `channel_listen_unix()` then binds the server socket inside that directory with permissions `0777 & ~umask`. The socketserver does not authenticate connecting clients and evaluates "expr" messages using `eval_client_expr_to_string()`, and "keystrokes" messages are inserted into the input buffer. With a permissive umask (e.g. `002` or `000`) the attacker can connect to the socket directly. With the common umask `022` a direct connect fails, but since the attacker owns the directory, they can still remove or replace the socket and impersonate the server towards clients. ## Impact Arbitrary Vim expression evaluation, and therefore arbitrary shell command execution, in the context of the user running Vim, on multi-user systems. Exploitation requires: * a Vim build with the `+socketserver` feature, used as server (e.g. using `--servername` or with `+autoservername`), * the attacker having a local account on the same system, * the socket directory being located in a shared directory such as `/tmp` (`$XDG_RUNTIME_DIR` is not affected, since it is only accessible by the user), * for direct code execution: a umask that makes the socket accessible by the attacker. ## Acknowledgements The Vim project would like to thank Calif.io and 360AlphaLab for independently reporting the issue. ## References The issue has been fixed as of Vim patch [v9.2.1308](https://github.com/vim/vim/releases/tag/v9.2.1308). - [Commit](https://github.com/vim/vim/commit/a448e0c6bc459d7dbeab581bcb76a0d) - [Github Security Advisory](https://github.com/vim/vim/security/advisories/GHSA-p99j-mfjp-r4cg)

Why it matters now

Fix Fixed Vim (vim): v9.2.1308

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—Vim (vim)< v9.2.1308v9.2.1308Patch availableGHSA-p99j-mfjp-r4cg
  • Vim (vim) Vendor— Affected < v9.2.1308 Fixed in v9.2.1308 Patch available GHSA-p99j-mfjp-r4cg

Remediation

Upgrade Vim to v9.2.1308 or later, which fixes the issue.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

  • Fix · GHSA-p99j-mfjp-r4cg Vim (vim) Fixed in v9.2.1308 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-p99j-mfjp-r4cg

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences