How severe is GHSA-wgh4-64f7-q3jq?

No CVSS score has been assigned to GHSA-wgh4-64f7-q3jq yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-wgh4-64f7-q3jq?

Affected package information for GHSA-wgh4-64f7-q3jq is not yet fully mapped. Check the official advisory links for details.

How do I fix GHSA-wgh4-64f7-q3jq?

Upgrade the affected component to the fixed release for GHSA-wgh4-64f7-q3jq, 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-wgh4-64f7-q3jq 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-wgh4-64f7-q3jq if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is GHSA-wgh4-64f7-q3jq actively exploited in the wild?

No public exploit code has been indexed for GHSA-wgh4-64f7-q3jq 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-wgh4-64f7-q3jq?

GHSA-wgh4-64f7-q3jq has an EPSS (Exploit Prediction Scoring System) score of 0.1%, placing it in the 2th 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-wgh4-64f7-q3jq?

GHSA-wgh4-64f7-q3jq is classified as Out-of-bounds Write (CWE-787). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-wgh4-64f7-q3jq published, and has it been updated?

GHSA-wgh4-64f7-q3jq was published on June 25, 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.

Vim: Out-of-bounds Write in Spell File Word Count

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-wgh4-64f7-q3jq.

EPSS Exploitation Probability

via FIRST.org ↗

0.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs2th percentile — riskier than 2% 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.0653, the tree_count_words() function in src/spellfile.c fills in the word-count fields of a spell-file word trie by walking it iteratively with a depth counter. The counter is bounded only by the trie structure itself; it is never checked against the size of the fixed MAXWLEN-element stack arrays it indexes (arridx[], curi[], wordcount[]). A crafted .spl/.sug file pair, loaded when the user invokes spell suggestion, can drive the descent arbitrarily deep, so the function writes past the end of those arrays. This is a stack out-of-bounds write that corrupts the call frame and crashes the editor. This vulnerability is fixed in 9.2.0653.

Affected Products

1 product · 1 configurations

Application

vimvim

< 9.2.0653

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-wgh4-64f7-q3jq, 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
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

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

This Moderate impact vulnerability in Vim's spell suggestion feature allows an attacker to cause a denial of service. By tricking a user into loading a specially crafted spell file and invoking spell suggestion, an out-of-bounds write can occur, leading to a crash of the editor. This requires user interaction and a…

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 6 Extended Lifecycle Support - EXTENSION	`vim-2:7.4.629-5.el6_10.4`	RHSA-2026:69128
Red Hat Enterprise Linux 7 Extended Lifecycle Support	`vim-2:7.4.629-8.el7_9.2`	RHSA-2026:68711
Red Hat Enterprise Linux 8	`vim-2:8.0.1763-31.el8_10`	RHSA-2026:48703
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

Frequently Asked Questions

Vim is an open source, command line text editor. Prior to 9.2.0653, the tree_count_words() function in src/spellfile.c fills in the word-count fields of a spell-file word trie by walking it iteratively with a depth counter. The counter is bounded only by the trie structure itself; it is never checked against the size of the fixed MAXWLEN-element stack arrays it indexes (arridx[], curi[], wordcount[]). A crafted .spl/.sug file pair, loaded when the user invokes spell suggestion, can drive the descent arbitrarily deep, so the function writes past the end of those arrays. This is a stack out-of-b

O3 Security · Impact-Aware SCA

Is GHSA-wgh4-64f7-q3jq in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works

Vim: Out-of-bounds Write in Spell File Word CountGHSA-wgh4-64f7-q3jq