VulnerabilityPublished 6 Feb 2026Updated 23 Feb 2026

CVE-2026-2008: abhiphile fermat-mcp · Code Injection

Affects abhiphile fermat-mcpSource CVE Database V5

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 11:07 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
abhiphilefermat-mcp	Affected =47f11def1cd37e45dd060f30cdce346cbdbd6f0a	Fixed in–

AI-suggested

Organizations should immediately audit their environments to identify deployments of abhiphile fermat-mcp, particularly those using versions up to commit 47f11def1cd37e45dd060f30cdce346cbdbd6f0a. Given the absence of an official patch, temporary mitigations include implementing strict input validation and sanitization on any interfaces accepting 'equations' arguments to prevent injection. Network-level controls such as firewall rules or segmentation should restrict access to the vulnerable service to trusted hosts only. Monitoring and logging of suspicious input patterns or anomalous execution behaviors related to eqn_chart function calls can aid early detection. Organizations should engage with the fermat-mcp maintainers or community to track patch releases and apply updates promptly once available. Additionally, consider deploying application-layer firewalls or runtime application self-protection (RASP) solutions that can detect and block code injection attempts. Finally, incorporate this vulnerability into incident response plans to prepare for potential exploitation scenarios.

Description

A vulnerability was detected in abhiphile fermat-mcp up to 47f11def1cd37e45dd060f30cdce346cbdbd6f0a. This vulnerability affects the function eqn_chart of the file fmcp/mpl_mcp/core/eqn_chart.py. Performing a manipulation of the argument equations results in code injection. It is possible to initiate the attack remotely. The exploit is now public and may be used. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available. The project was informed of the problem early through an issue report but has not responded yet.

Impact

The primary impact of CVE-2026-2008 is the potential for remote code execution on systems running vulnerable versions of fermat-mcp, which could lead to unauthorized control over affected systems. This can compromise system confidentiality, integrity, and availability, enabling attackers to execute arbitrary commands, deploy malware, or pivot within networks. Since fermat-mcp is a specialized software component, organizations relying on it for critical operations may face service disruptions, data breaches, or further compromise. The lack of authentication and user interaction requirements lowers the barrier for exploitation, increasing the risk of automated attacks. The rolling release nature of the product complicates patch deployment, potentially prolonging exposure. While no widespread exploitation is currently reported, the public exploit availability suggests that opportunistic attackers may target vulnerable deployments, especially in environments where fermat-mcp is integrated into larger systems.

Summary

CVE-2026-2008 identifies a code injection vulnerability in the abhiphile fermat-mcp software, affecting the eqn_chart function within the fmcp/mpl_mcp/core/eqn_chart.py source file. The vulnerability arises from improper handling and sanitization of the 'equations' argument, which can be manipulated remotely to inject malicious code. This flaw allows attackers to execute arbitrary code on the affected system without requiring authentication or user interaction, leveraging network access to the vulnerable service. The vulnerability has a CVSS 4.0 score of 5.3, indicating a medium severity level due to its network attack vector, low attack complexity, and lack of required privileges or user interaction, but with limited impact on confidentiality, integrity, and availability. The public availability of exploit code increases the urgency for organizations to assess and mitigate this risk promptly.

References

Community reviews

Loading reviews…