CVE-2026-33412

HIGHNVD 7.37.3
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.3 under NVD CVSS v3. EPSS exploit probability: 0.8%, top 46% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this week
7.3
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.3Exploit: NoneExposed: 0

A fix is available — apply it.

Vim is an open source, command line text editor. Prior to version 9.2.0202, a command injection vulnerability exists in Vim's glob() function on Unix-like systems. By including a newline character (\n) in a pattern passed to glob(), an attacker may be able to execute arbitrary shell commands. This vulnerability depends on the user's 'shell' setting. This issue has been patched in version 9.2.0202.

CVSS v3
7.3
EG Score
7.3(medium)
EG Risk
33(Track)
EG Risk 33/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity73% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
53.9%
KEV
Not listed

Published

March 24, 2026

Last Modified

July 15, 2026

Advisory Details (9)

Auto-updated Jul 15, 2026
Patch available. Sources: github_commit, github, redhat.
generic

oss-security - [vim-security]: Command injection via newline in glob() affects Vim < 9.2.0202

http://www.openwall.com/lists/oss-security/2026/03/19/10
github Patch Available

Command injection via newline in glob() affects Vim < 9.2.0202 · Advisory · vim/vim · GitHub

https://github.com/vim/vim/security/advisories/GHSA-w5jw-f54h-x46c
github_commit

commit 645ed6597d1e (vim/vim)

Fix landed in vim/vim commit 645ed6597d1e — awaiting tagged release

https://github.com/vim/vim/commit/645ed6597d1ea896c712cd7ddbb6edee79577e9a

Patch Availability(30)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhaiis/model-opt-cuda-rhel9:17806819842026-06-10redhat
redhatrhcos-417.94.202605112123-02026-05-20redhat
redhatrhcos-415.92.202605060220-02026-05-13redhat
redhatrhcos-414.92.202605060243-02026-05-13redhat
redhatrhaiis/vllm-spyre-rhel9:17782445462026-05-12redhat
redhatrhaiis/vllm-rocm-rhel9:17782445312026-05-11redhat
redhatrhaiis/model-opt-cuda-rhel9:17782445592026-05-11redhat
redhatrhcos-412.86.202604281506-02026-05-08redhat
redhatrhcos-416.94.202604211449-02026-04-30redhat
redhatrhui5/rhua-tp-rhel9:17774595042026-04-29redhat
redhatrhui5/rhua-rhel9:17768688422026-04-23redhat
redhatrhcos-418.94.202604140044-02026-04-22redhat
redhatinsights-proxy/insights-proxy-container-rhel9:17768689612026-04-22redhat
redhatrhcos-4.19.9.6.202604080618-02026-04-16redhat
redhatrhcos-413.92.202604080111-02026-04-16redhat
redhatvim-2:8.2.2637-23.el9_7.22026-04-15redhat
redhatvim-2:9.1.083-6.el10_1.32026-04-13redhat
redhatrhaiis/vllm-cuda-rhel9:17757405632026-04-09redhat
redhatvim-2:8.0.1763-13.el8_2.12026-04-07redhat
redhatvim-2:8.0.1763-20.el8_8.12026-04-07redhat
redhatvim-2:8.0.1763-19.el8_6.52026-04-07redhat
redhatvim-2:7.4.629-5.el6_10.32026-04-07redhat
redhatvim-2:8.0.1763-15.el8_4.12026-04-07redhat
redhatvim-2:8.0.1763-22.el8_10.12026-04-07redhat
redhatvim-2:7.4.629-8.el7_9.12026-04-06redhat
redhatvim-2:8.2.2637-20.el9_2.12026-04-06redhat
redhatvim-2:8.2.2637-16.el9_0.42026-04-06redhat
redhatvim-2:8.2.2637-22.el9_6.22026-04-02redhat
redhatvim-2:8.2.2637-20.el9_4.22026-04-02redhat
redhatvim-2:9.1.083-5.el10_0.22026-04-02redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(10)

Data Freshness Timeline

(refreshed 9× in last 7d / 34× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 03:09 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:24 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-18 06:59 UTCOSV refresh
  9. 2026-07-16 17:03 UTCEPSS rescore
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 16:57 UTCEPSS rescore
  12. 2026-07-15 02:22 UTCNVD updateCVSS v3 → 7.3 · severity → HIGH
  13. 2026-07-15 02:00 UTCEPSS rescore
  14. 2026-07-15 02:00 UTCEPSS rescore
  15. 2026-07-15 01:21 UTCMITRE cvelistV5CVSS v3 → 5.6 · severity → MEDIUM
  16. 2026-07-13 22:30 UTCEPSS rescore
  17. 2026-07-13 06:13 UTCEPSS rescore
  18. 2026-07-13 06:13 UTCEPSS rescore
  19. 2026-07-12 05:46 UTCEPSS rescore
  20. 2026-07-11 08:27 UTCEPSS rescore
  21. 2026-07-09 19:10 UTCEPSS rescore
  22. 2026-07-08 15:15 UTCEPSS rescore
  23. 2026-07-07 13:46 UTCEPSS rescore
  24. 2026-07-06 16:27 UTCEPSS rescore
  25. 2026-07-06 16:27 UTCEPSS rescore
Show 9 more
  1. 2026-07-06 02:23 UTCEPSS rescore
  2. 2026-07-06 02:23 UTCEPSS rescore
  3. 2026-07-05 02:30 UTCEPSS rescore
  4. 2026-07-04 06:31 UTCEPSS rescore
  5. 2026-07-01 15:06 UTCEPSS rescore
  6. 2026-06-30 23:22 UTCEPSS rescore
  7. 2026-06-30 04:37 UTCEG score recompute
  8. 2026-06-30 04:37 UTCVendor advisory
  9. 2026-06-30 04:32 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-33412?
CVE-2026-33412 is a high vulnerability published on March 24, 2026. Vim is an open source, command line text editor. Prior to version 9.2.0202, a command injection vulnerability exists in Vim's glob() function on Unix-like systems. By including a newline character (\n) in a pattern passed to glob(), an attacker may be able to execute arbitrary shell commands. This…
When was CVE-2026-33412 disclosed?
CVE-2026-33412 was first published in the National Vulnerability Database on March 24, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-33412 actively exploited?
CVE-2026-33412 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 53.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-33412?
CVE-2026-33412 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-33412?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-33412, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-33412

Explore →

Is Your Infrastructure Affected by CVE-2026-33412?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.