dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-7785

HIGH · 7.3 CVSS v3.1 Published 2026-05-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges 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 security flaw has been discovered in A-G-U-P-T-A wireshark-mcp edaf604416fbc94a201b4043092d4a1b09a12275/400c3da70074f22f3cce7ccb65304cafc7089c89. This affects the function quick_capture of the file pyshark_mcp.py. The manipulation results in os command injection. The attack may be launched remotely. The exploit has been released to the public and may be used for attacks. This product operates on a rolling release basis, ensuring continuous delivery. Consequently, there are no version details for either affected or updated releases. 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 · high confidence

OS command injection vulnerability in the quick_capture function of pyshark_mcp.py in the wireshark-mcp project. The function fails to properly sanitize input before passing it to OS command execution, allowing remote attackers to inject and execute arbitrary shell commands.

MitigationReplace direct shell command execution with parameterized methods (e.g., subprocess with shell=False, argument lists) and implement strict input validation to prevent command injection. Alternatively, use safe API wrappers that do not invoke shell interpretation.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify wireshark-mcp package installation
    Run 'pip show wireshark-mcp' or 'pip list | grep -i wireshark' to check if the wireshark-mcp package is installed in your environment
    Affected if The package is not installed - not vulnerable. If installed, continue to next checks.
  2. Locate pyshark_mcp.py source file
    Run 'pip show -f wireshark-mcp' to find the installed file path, then locate pyshark_mcp.py in the package directory
    Affected if File not found - not applicable. If found, proceed to examine it.
  3. Inspect quick_capture function for command execution
    Open pyshark_mcp.py and locate the 'def quick_capture' function. Search for os.system, subprocess.call with shell=True, subprocess.run with shell=True, or similar OS command execution methods within this function
    Affected if The function contains direct OS command execution (os.system, subprocess with shell=True) that processes user input without sanitization - potentially vulnerable.
  4. Check for input validation in quick_capture
    Examine the quick_capture function code to see if input parameters (especially those passed to shell commands) are sanitized, validated, or use parameterized methods instead of string concatenation
    Affected if Input is passed directly to shell commands without sanitization, escaping, or use of shell=False - vulnerable to command injection.
  5. Determine if quick_capture is exposed
    Review how quick_capture is called - check if it's exposed via API endpoints, CLI interfaces, or other entry points that accept external input
    Affected if The function can be triggered with user-controlled input from network sources - vulnerability is exploitable.

If wireshark-mcp is installed, pyshark_mcp.py contains the quick_capture function with unsanitized input passed to shell execution, and that function is accessible with external input, the environment is affected by CVE-2026-7785.

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

Replace direct shell command execution with parameterized methods (e.g., subprocess with shell=False, argument lists) and implement strict input validation to prevent command injection. Alternatively, use safe API wrappers that do not invoke shell interpretation.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7785 — 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-7785 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