dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-44717

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
MCP Calculate Server is a mathematical calculation service based on MCP protocol and SymPy library. Prior to 0.1.1, the use of eval() to evaluate mathematical expressions without proper input sanitization leads to remote code execution. This vulnerability is fixed in 0.1.1.

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

The MCP Calculate Server uses Python's eval() function to evaluate mathematical expressions from user input without sanitization, allowing attackers to inject and execute arbitrary Python code remotely. This is a critical RCE vulnerability (CVSS 9.8) stemming from improper use of eval() instead of SymPy's safe evaluation methods.

MitigationUpgrade to version 0.1.1 or later which implements proper input sanitization using SymPy's safe evaluation methods instead of eval(). If upgrade is not possible, replace eval() with SymPy's sympify(evaluate=False) or implement a restricted expression parser.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Locate MCP Calculate Server installation
    Search for files named 'calculate', 'mcp_calculate', or similar. Check common installation paths like /opt/, /usr/local/, or the user's home directory. Look for Python packages: pip list | grep -i calculate
    Affected if The MCP Calculate Server is installed on the system
  2. Identify the expression handler code
    Find Python source files in the installation that handle mathematical expressions. Look for files with functions processing user input for calculations. Common patterns: search for 'eval(', 'calculate', 'expression' in .py files
    Affected if Code exists that evaluates mathematical expressions from input
  3. Verify eval() is used without sanitization
    Open the expression handler source file and inspect the code that processes input. Look for direct calls to eval() or similar unsafe functions without input validation, sanitization, or use of safe parsing alternatives
    Affected if The code contains eval() being called on raw user input without validation or safe parsing wrappers
  4. Check if the server is network-accessible
    Determine if the MCP Calculate Server exposes a network service (HTTP, socket, or other). Review configuration files, startup scripts, or service definitions for listening ports and bind addresses
    Affected if The server accepts remote connections and can process expressions from network sources
  5. Test for the vulnerability
    If the server is accessible, send a test mathematical expression containing Python code (e.g., '1+1' as a baseline, then a benign test like '__import__("os").system("echo test")' to observe if code executes). Use caution in production environments
    Affected if Arbitrary Python code in the expression input is executed by the server
  6. Check installed version
    If a version can be determined (pip show, package metadata, or --version flag), compare it to the fixed version 0.1.1. The absence of a version or a version below 0.1.1 indicates potential vulnerability
    Affected if The installed version is unknown or lower than 0.1.1

If the MCP Calculate Server is installed and its expression handling code directly uses eval() on unsanitized user input (whether locally or over a network), the environment is affected by CVE-2026-44717.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 0.1.1 or later which implements proper input sanitization using SymPy's safe evaluation methods instead of eval(). If upgrade is not possible, replace eval() with SymPy's sympify(evaluate=False) or implement a restricted expression parser.

Recommended fix High confidence

0.1.1

  1. Check the current version of MCP Calculate Server installed in your environment
  2. Upgrade MCP Calculate Server to version 0.1.1 or later
  3. Verify the upgrade was successful by checking the installed version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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