dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-0758

HIGH · 7.8 CVSS v3.0 Published 2026-01-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
mcp-server-siri-shortcuts shortcutName Command Injection Privilege Escalation Vulnerability. This vulnerability allows local attackers to escalate privileges on affected installations of mcp-server-siri-shortcuts. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability. The specific flaw exists within the shortcutName parameter. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of the service account. Was ZDI-CAN-27910.

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

Command injection vulnerability in the shortcutName parameter of mcp-server-siri-shortcuts. The application passes user-supplied input directly to a system call without validation, allowing injection of shell commands. An attacker with low-privileged code execution can exploit this to escalate to service account privileges and execute arbitrary code.

MitigationImplement strict input validation/sanitization on the shortcutName parameter and refactor to use safe APIs or parameterized commands instead of direct system calls with user input.

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

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

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. Identify if mcp-server-siri-shortcuts is installed
    Search for the package in node_modules, check for running processes named mcp-server-siri-shortcuts, or look for service definitions. Common locations: npm list -g | grep mcp, or ps aux | grep siri-shortcuts
    Affected if The product is present in the environment
  2. Determine the installed version
    Run npm list mcp-server-siri-shortcuts, check package.json dependencies, or query the service version if it exposes a --version flag
    Affected if Unable to verify version against any fixed releases or version comparison shows it exists
  3. Locate the code handling the shortcutName parameter
    Search source code for the shortcutName parameter handling. Look for files in the mcp-server-siri-shortcuts package that handle this parameter, typically in route handlers or command processing functions
    Affected if The code that processes shortcutName is found in the codebase
  4. Inspect for vulnerable system call pattern
    Examine the code handling shortcutName for direct system() or exec() calls with unsanitized input. Search for patterns like system(shortcutName), exec("..." + shortcutName), or child_process calls without input sanitization
    Affected if User-supplied shortcutName parameter is passed directly to a shell execution function without validation or escaping
  5. Verify if external input can reach the vulnerable function
    Check API endpoints, CLI interfaces, or IPC mechanisms that accept shortcutName input. Determine if these interfaces are accessible to low-privileged users or external attackers
    Affected if The shortcutName parameter accepts input from untrusted sources (user HTTP parameters, CLI arguments, or external processes)

User is affected if mcp-server-siri-shortcuts is installed and the shortcutName parameter accepts untrusted input that flows to unsanitized system calls in the code.

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/sanitization on the shortcutName parameter and refactor to use safe APIs or parameterized commands instead of direct system calls with user input.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,950
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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