How severe is CVE-2005-0069?

CVE-2005-0069 has a CVSS 2.0 base score of 4.6, rated medium severity.

Is CVE-2005-0069 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (28th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2005-0069?

CVE-2005-0069 primarily affects Vim Development Group Vim. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2005-0069?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2005-0069 published?

CVE-2005-0069 was published on 2005-01-13 and last updated on 2026-06-16.

CVE-2005-0069

CVE-2005-0069 is a medium-severity vulnerability in Vim Development Group Vim with a CVSS 2.0 base score of 4.6. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 2.0 base score 4.6)
EPSS exploit prediction: 0% (28th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Vim Development Group Vim
Published: 2005-01-13
Last modified: 2026-06-16

Description

The (1) tcltags or (2) vimspell.sh scripts in vim 6.3 allow local users to overwrite or create arbitrary files via a symlink attack on temporary files.

Frequently asked questions

What is CVE-2005-0069?: The (1) tcltags or (2) vimspell.sh scripts in vim 6.3 allow local users to overwrite or create arbitrary files via a symlink attack on temporary files.
How severe is CVE-2005-0069?: CVE-2005-0069 has a CVSS 2.0 base score of 4.6, rated medium severity.
Is CVE-2005-0069 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (28th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2005-0069?: CVE-2005-0069 primarily affects Vim Development Group Vim. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2005-0069?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2005-0069 published?: CVE-2005-0069 was published on 2005-01-13 and last updated on 2026-06-16.

References

Affected products (4)

cpe:2.3:a:vim_development_group:vim:6.3.011:*:*:*:*:*:*:*
cpe:2.3:a:vim_development_group:vim:6.3.025:*:*:*:*:*:*:*
cpe:2.3:a:vim_development_group:vim:6.3.030:*:*:*:*:*:*:*
cpe:2.3:a:vim_development_group:vim:6.3.044:*:*:*:*:*:*:*

More vulnerabilities in Vim Development Group Vim

CVE-2005-2368 — Critical (CVSS 9.3): vim 6.3 before 6.3.082, with modelines enabled, allows external user-assisted attackers to execute arbitrary commands…
CVE-2007-2438 — High (CVSS 7.6): The sandbox for vim allows dangerous functions such as (1) writefile, (2) feedkeys, and (3) system, which might allow…
CVE-2004-1138 — High (CVSS 7.2): VIM before 6.3 and gVim before 6.3 allow local users to execute arbitrary commands via a file containing a crafted…
CVE-2007-2953 — Medium (CVSS 6.8): Format string vulnerability in the helptags_one function in src/ex_cmds.c in Vim 6.4 and earlier, and 7.x up to 7.1,…
CVE-2001-0408 — Medium (CVSS 5.1): vim (aka gvim) processes VIM control codes that are embedded in a file, which could allow attackers to execute…
CVE-2002-1377 — Medium (CVSS 4.6): vim 6.0 and 6.1, and possibly other versions, allows attackers to execute arbitrary commands using the libcall feature…

All CVEs affecting Vim Development Group Vim →