# CVE-2026-2130: mcp-maigret — Fixed in 1.0.13

📦 npm

Not in CISA KEV

# CVE-2026-2130 — mcp-maigret

[Fix: BurtTheCoder/mcp-maigret@b1ae073](https://github.com/BurtTheCoder/mcp-maigret/commit/b1ae073c4b3e789ab8de36dc6ca8111ae9399e7a)

CVE-2026-2130 is a CWE-74 vulnerability in mcp-maigret. A fix is available for mcp-maigret — see the affected versions and patch details below.

BurtTheCoder mcp-maigret search\_username index.ts command injection

Also known as[GHSA-2g7v-hghf-grg4](/vulnerability/GHSA-2g7v-hghf-grg4)

Published

Feb 8, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

## Exploitation Status

### No confirmed exploitation observed yet

-   CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-2130.

## EPSS Exploitation Probability

[via FIRST.org ↗](https://www.first.org/epss/)

2.0%probability of exploitation in next 30 days

Lower Risk\-0.03%

Lower risk than most CVEs81th percentile — riskier than 81% of all scored CVEsHighest risk

0.00%0.85%1.70%2.56%0.2%2.0%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/).

## Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

1other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

`mcp-maigret`npm

918downloads / week

## Description

A vulnerability was determined in BurtTheCoder mcp-maigret up to 1.0.12. This affects an unknown part of the file src/index.ts of the component search\_username. Executing a manipulation of the argument Username can lead to command injection. The attack may be launched remotely. Upgrading to version 1.0.13 is able to mitigate this issue. This patch is called b1ae073c4b3e789ab8de36dc6ca8111ae9399e7a. Upgrading the affected component is advised.

## Affected Packages

1 total 1 fixed

Ecosystem

Package

Vulnerable range

Fix

📦npm

`mcp-maigret` 

all versions

1.0.13`npm install mcp-maigret@1.0.13`

## Affected Products

1 product · 1 configurations

Application

`maigret mcp server`burtthecoder

≤ 1.0.12

range

## Detection & mitigation playbook

Open-source dependency

1.  ### Detect
    
    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mcp-maigret, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
    
2.  ### Fix
    
    Update mcp-maigret to 1.0.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-2130 is resolved across your whole dependency graph.
    
3.  ### Workarounds
    
    Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
    

## Frequently Asked Questions

A vulnerability was determined in BurtTheCoder mcp-maigret up to 1.0.12. This affects an unknown part of the file src/index.ts of the component search\_username. Executing a manipulation of the argument Username can lead to command injection. The attack may be launched remotely. Upgrading to version 1.0.13 is able to mitigate this issue. This patch is called b1ae073c4b3e789ab8de36dc6ca8111ae9399e7a. Upgrading the affected component is advised.

O3 Security · Impact-Aware SCA

### Is CVE-2026-2130 in your dependencies?

Find it across npm, including transitive dependencies.

[Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)