LiveActive security incident?Get immediate response
CVE Record

CVE-2026-33412: Vim affected by Command injection via newline in glob()

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.

HighCVSS 7.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Vim versions before 9.2.0202 on Unix-like systems can allow an attacker to turn a specially formed glob() pattern containing a newline into shell-command execution. Successful exploitation could compromise the confidentiality, integrity, and availability of data accessible to the Vim user. The published assessment requires local access, low privileges, and user interaction.

Executive priority

Treat this as a high-priority workstation and administration-tool update, especially where Vim handles untrusted content or runs under privileged operational accounts. The impact can be severe, but the documented prerequisites reduce immediacy compared with remotely exploitable flaws. Track remediation promptly; emergency response is not supported solely by the supplied exploitation evidence.

Technical view

CVE-2026-33412 is a CWE-78 command-injection flaw in Vim's glob() handling. A newline embedded in a supplied pattern may be interpreted through the configured shell, enabling arbitrary commands with the Vim user's permissions. Exploitability depends on the user's 'shell' setting. CVSS 3.1 is 7.3: AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H.

Likely exposure

Exposure is most likely on Unix-like systems running Vim earlier than 9.2.0202 where attacker-influenced patterns reach glob(). The supplied evidence does not identify every vulnerable workflow or confirm that all configurations are exploitable. Systems using vendor-backported packages require vendor advisory or package-status verification rather than upstream version comparison alone.

Exploitation context

The CVSS vector describes local exploitation requiring low privileges and user interaction, with low attack complexity. Execution occurs with the affected Vim user's authority, not automatically with elevated privileges. The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation; exploitation status should therefore be treated as unconfirmed.

Researcher notes

The security boundary is the construction and shell processing of glob() patterns containing newlines. The patch commit and advisory should be used to assess backports. Configuration dependence is explicitly noted, but the source bundle does not provide enough detail to classify individual 'shell' values as safe or vulnerable. Avoid equating package version strings with exposure when vendors backport fixes.

Mitigation direction

  • Upgrade upstream Vim to version 9.2.0202 or later.
  • For distribution-managed Vim, install the applicable vendor security update or confirmed backport.
  • Prioritize shared administration hosts, developer workstations, and systems processing untrusted Vim-related input.
  • Until updated, restrict untrusted input from reaching workflows that pass patterns to glob().

Validation and detection

  • Inventory Vim versions on Unix-like endpoints and compare them with 9.2.0202.
  • Check distribution advisories to confirm whether older package versions contain a backported fix.
  • Review the Vim 'shell' setting and identify workflows supplying external patterns to glob().
  • After updating, verify package status and rerun the organization's authenticated vulnerability scan.
Prepared
Confidence
high
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-78: Command execution behavior lookup

Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-33412 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
3ADP providers
37Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.3CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H1.35.9redhat-SADP
5.6CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:H/A:N1.34.2GitHub_M

Vulnerability scoring details

Base CVSS 3.1 score

7.3High
CVSS 3.1 vector shape for CVE-2026-33412Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPvim: Vim: Arbitrary code execution via command injection in glob() function
other:Red Hat severity ratingcvssV3_1
  • 2026-03-24T20:02:21.511Z: Reported to Red Hat.
  • 2026-03-24T19:43:07.219Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
vimvim< 9.2.0202Listed
Weakness

CWE details

CWE-78

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-78 · source CWE mapping

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs