dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-10279

MEDIUM · 6.3 CVSS v3.1 Published 2026-06-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was identified in hiraishikentaro wezterm-mcp 0.1.0. The affected element is an unknown function of the file src/wezterm_executor.ts of the component switch_pane/write_to_specific_pane. The manipulation of the argument request.params.arguments.pane_id leads to os command injection. The attack can be initiated remotely. The exploit is publicly available and might be used. The project was informed of the problem early through an issue report but has not responded yet.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

OS command injection vulnerability in wezterm-mcp version 0.1.0 where the pane_id argument passed to the switch_pane/write_to_specific_pane function in src/wezterm_executor.ts is not properly sanitized before being used in shell command execution.

MitigationImplement strict input validation and sanitization on the pane_id parameter, or refactor to avoid shell command execution entirely by using parameterized APIs if available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm wezterm-mcp is installed
    Check for the wezterm-mcp package in your system using your package manager, or look for the binary/script (commonly named wezterm-mcp) in your PATH or installation directory.
    Affected if The package or binary named wezterm-mcp is present on the system.
  2. Identify the installed version
    Run 'wezterm-mcp --version' or check the package metadata (e.g., 'pip show wezterm-mcp', npm list wezterm-mcp, or your system package manager's query command) to retrieve the version number.
    Affected if The version returned is exactly 0.1.0.
  3. Verify the MCP server is running
    Check if the wezterm-mcp server process is active and listening for connections, or inspect your MCP server configuration to confirm wezterm-mcp is registered as an active server.
    Affected if The wezterm-mcp server is running and accessible to clients.
  4. Confirm the vulnerable functions are exposed
    Inspect the MCP server's exposed methods (check the server's capabilities/endpoint list or source code for switch_pane and write_to_specific_pane function definitions) to verify these functions are available.
    Affected if The switch_pane or write_to_specific_pane functions are listed as available MCP methods.

You are affected if wezterm-mcp version 0.1.0 is installed, the MCP server is running, and the switch_pane or write_to_specific_pane functions are exposed to clients who can supply the pane_id parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and sanitization on the pane_id parameter, or refactor to avoid shell command execution entirely by using parameterized APIs if available.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,180
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10279 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-10279 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data