How severe is GHSA-fh26-8f79-wj97?

No CVSS score has been assigned to GHSA-fh26-8f79-wj97 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-fh26-8f79-wj97?

Affected package information for GHSA-fh26-8f79-wj97 is not yet fully mapped. Check the official advisory links for details.

How do I fix GHSA-fh26-8f79-wj97?

Upgrade the affected component to the fixed release for GHSA-fh26-8f79-wj97, or apply your distribution's backported patch — distro builds are often patched at an older version number, so check your vendor's advisory rather than the upstream version alone.

How do I detect GHSA-fh26-8f79-wj97 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate GHSA-fh26-8f79-wj97 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is GHSA-fh26-8f79-wj97 actively exploited in the wild?

No public exploit code has been indexed for GHSA-fh26-8f79-wj97 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-fh26-8f79-wj97?

GHSA-fh26-8f79-wj97 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 11th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-fh26-8f79-wj97?

GHSA-fh26-8f79-wj97 is classified as Code Injection (CWE-94). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-fh26-8f79-wj97 published, and has it been updated?

GHSA-fh26-8f79-wj97 was published on July 9, 2026 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-fh26-8f79-wj97: vim

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-fh26-8f79-wj97.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs11th percentile — riskier than 11% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

Vim is an open source, command line text editor. Prior to 9.2.0736, the PHP omni-completion script in runtime/autoload/phpcomplete.vim interpolates a class or trait name, taken from the contents of the edited buffer, into a search() pattern that is run via win_execute() without escaping. A name containing a single quote can terminate the search() string argument early, and because the bar is honored as an Ex command separator, the remainder of the name is run as Ex commands; via the :! command this allows arbitrary operating-system command execution when a victim opens a crafted PHP file and invokes omni-completion. This issue is fixed in version 9.2.0736.

Affected Products

1 product · 1 configurations

Application

vimvim

< 9.2.0736

range

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Fix
Upgrade the affected component to the fixed release for GHSA-fh26-8f79-wj97, or apply your distribution's backported patch — distro builds are often patched at an older version number, so check your vendor's advisory rather than the upstream version alone.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Red Hat Product Security has rated this vulnerability as having a Moderate impact. While successful exploitation allows for arbitrary operating-system command execution when a user opens a crafted PHP file and triggers omni-completion, this feature is disabled by default in Red Hat products. The requirement for a…

Workaround published by Red Hat

Users should exercise caution when opening untrusted PHP files and avoid invoking omni-completion on them. To prevent exploitation, the PHP omni-completion script can be disabled by moving or renaming `phpcomplete.vim`. For example, execute `mv /usr/share/vim/vim*/autoload/phpcomplete.vim /usr/share/vim/vim*/autoload/phpcomplete.vim.bak`. This action will disable PHP omni-completion functionality. A restart of Vim is necessary for this change to take effect.

Source: Red Hat security advisory for GHSA-fh26-8f79-wj97 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat Enterprise Linux 10	`vim-2:9.1.083-9.el10_2.12`	RHSA-2026:48650
Red Hat Enterprise Linux 10.0 Extended Update Support	`vim-2:9.1.083-5.el10_0.4`	RHSA-2026:55431
Red Hat Enterprise Linux 9	`vim-2:8.2.2637-26.el9_8.13`	RHSA-2026:47982
Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions	`vim-2:8.2.2637-20.el9_2.3`	RHSA-2026:72466
Red Hat Enterprise Linux 9.4 Update Services for SAP Solutions	`vim-2:8.2.2637-20.el9_4.4`	RHSA-2026:72465
Red Hat Enterprise Linux 9.6 Extended Update Support	`vim-2:8.2.2637-22.el9_6.4`	RHSA-2026:70818
Red Hat OpenShift Container Platform 4.22	`rhcos-4.22.9.8.202608130832-0`	RHSA-2026:54769
Red Hat AI Inference Server 3.2	`rhaiis/model-opt-cuda-rhel9:1790621714`	RHSA-2026:73859

UbuntuHIGH

USN-8541-1Ubuntu

Frequently Asked Questions

Vim is an open source, command line text editor. Prior to 9.2.0736, the PHP omni-completion script in runtime/autoload/phpcomplete.vim interpolates a class or trait name, taken from the contents of the edited buffer, into a search() pattern that is run via win_execute() without escaping. A name containing a single quote can terminate the search() string argument early, and because the bar is honored as an Ex command separator, the remainder of the name is run as Ex commands; via the :! command this allows arbitrary operating-system command execution when a victim opens a crafted PHP file and i

O3 Security · Impact-Aware SCA

Is GHSA-fh26-8f79-wj97 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works

GHSA-fh26-8f79-wj97 — vim