An issue in @justice8096/sagemath-mcp-server 1.0.1 allows a remote attacker to execute arbitrary code via the escapeShellString and…
Only local-execution mode of @justice8096/sagemath-mcp-server 1.0.1 and earlier is affected, the mode used when Sage is installed locally; the Docker path is not. No vendor rating or fix is listed in the checked facts.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
The @justice8096/sagemath-mcp-server package, a SageMath integration server for the Model Context Protocol, is affected by this vulnerability. A remote attacker could exploit flaws in its input escaping and code sanitization functions to run arbitrary code on the host system.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
An issue in @justice8096/sagemath-mcp-server 1.0.1 allows a remote attacker to execute arbitrary code via the escapeShellString and sanitizeCode functions.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- @justice8096/sagemath-mcp-servernpm
through 1.0.1
References 3
GitHub · justice8096/sagemath-mcp-server
stillosdigitalholdings.com
Questions about CVE-2026-106763
What does this mean?
The flaw lets tool arguments supplied to the Sage math tools run commands on the host. The advisory notes this can be reached through indirect prompt injection.Source: github.com
Am I affected, and how do I check?
Versions 1.0.1 and earlier are listed as affected. The exposure is in local-execution mode, which the server auto-selects when Sage is installed locally; the Docker path is not affected because it passes the program as an argument array. To check the setup, compare the installed package version against 1.0.1 and confirm whether Sage runs locally or through Docker.Source: github.com
What should I do about it?
The checked facts name no fixed version, so no upgrade target can be confirmed. Check the package's release notes for a later version that addresses this issue.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What if there's no patch?
Since the Docker path is unaffected, running the server through Docker instead of local mode limits the exposure to the local-execution path. The checked facts list no other workaround.Source: github.com