On this page (7 sections)

Ubuntu published USN-9127-1 on 17 November 2026 for Syntastic, a syntax checking plugin for Vim. The notice summarizes the problem as the plugin possibly running programs with your login rights if it opened a specially crafted file, and it references CVE-2018-11319.

This matters most to developers and administrators who use Vim with the vim-syntastic package on Ubuntu 18.04 LTS, especially on shared servers or machines where they open code from untrusted sources. The notice does not state a severity score, so none is given here.

What happened

Ubuntu reports that Syntastic looked in the current directory and in its parent directories for checker configuration files. If a user were tricked into checking a file inside a directory an attacker controls, the attacker could possibly achieve arbitrary code execution. Ubuntu's wording is cautious ("possibly"), and the notice gives no further exploit detail.

The fix changes the behavior. After the update, Syntastic reads only the checker configuration files that you name explicitly in the *_config_file options, instead of searching the directory tree for them.

Why this kind of flaw matters

The weakness class is easy to understand without exploit specifics. A tool that automatically trusts configuration found next to the file you are editing is trusting whoever controls that folder. Configuration for a syntax checker can influence which programs run, so loading it from an untrusted location can turn "open a file" into "run someone else's commands" under your account.

Any code would run with your own privileges, so the impact depends on who you are. For a regular user it exposes that user's files and keys. For an administrator who opens a file while logged in with elevated rights, the consequences are larger.

Who is realistically exposed

  • People running Ubuntu 18.04 LTS with the vim-syntastic package installed and enabled in Vim.
  • Developers and admins who open files from cloned repositories, downloaded archives, shared folders or other users' home directories.
  • Shared build or jump servers where several people can write to directories that others later open files from.

The notice lists only Ubuntu 18.04 LTS. It says nothing about other Ubuntu releases or other distributions, so do not assume either way; check your own package source.

How to check your exposure

This read-only command shows whether vim-syntastic is installed and which version. On 18.04, a version older than 3.8.0-1ubuntu0.1~esm1 means the fix is not applied.

Check the installed vim-syntastic version (Ubuntu/Debian)Shell
dpkg -l vim-syntastic

This read-only command prints the Ubuntu release you are running, so you know whether the notice applies.

Show the Ubuntu release (run on the machine)Shell
lsb_release -a

What to do now

Ubuntu says a standard system update makes the necessary changes, and that the fix for 18.04 is available through Ubuntu Pro via ESM Apps. Ubuntu notes Pro is free for up to five machines. The notice adds that a community fix might become publicly available in the future.

  1. Run the version check above on every Ubuntu 18.04 LTS machine where Vim is used.
  2. If Ubuntu Pro with ESM Apps is enabled, apply a normal system update and confirm with dpkg that vim-syntastic reaches 3.8.0-1ubuntu0.1~esm1.
  3. If Ubuntu Pro is not enabled, the fixed package will not be offered by the update. Decide whether to enable Pro on the affected machines or remove the plugin if you do not need it.
  4. Until patched, avoid running syntax checks on files from untrusted directories, such as unreviewed clones or downloads.
  5. Do not open untrusted files in Vim from a root shell.
  6. Record which hosts were fixed so older 18.04 systems are not forgotten.

This command refreshes the package lists and upgrades installed packages through the normal Ubuntu mechanism. It delivers the fixed vim-syntastic only when Ubuntu Pro with ESM Apps is enabled on the machine. Run it with sudo, then rerun the dpkg check above and look for 3.8.0-1ubuntu0.1~esm1.

Apply updates on Ubuntu 18.04 (fix arrives only with Ubuntu Pro ESM Apps enabled)Shell
sudo apt update && sudo apt upgrade
This command upgrades every package with an available update, which can change other software on the machine. On production servers, run it in a maintenance window.

Detection and monitoring afterwards

The notice describes no indicators of compromise and no observed attacks, so there is no signature to hunt for. Reasonable follow-up is general hygiene: on machines where untrusted files were opened before patching, review shell history and recently modified files, and watch for unexpected processes started from editor sessions.

Plugins like this belong to a wider habit of tracking developer tooling on servers. Keeping a short inventory of editor plugins and checking it when new Ubuntu notices appear is cheaper than investigating afterwards. For public-facing sites, Webforta Scan examines your website from the outside, but it cannot see what is installed in an editor on a server, so package version checks remain your job. See also our guide to website security for small business.

Context and open questions

  • The notice references CVE-2018-11319, but the research provided contains no CVSS score or CVE record text, so severity is unconfirmed.
  • The notice contains no information on active exploitation.
  • Ubuntu is the only source here. It is the primary advisory, but there is no independent analysis yet.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. USN-9127-1: Syntastic vulnerability | Ubuntu security notices | Ubuntuubuntu.com ·
  • Ubuntu
  • USN
  • Syntastic
  • Vim
  • CVE-2018-11319