CVE-2026-2130
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 · uneditedA 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.
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 confidenceA command injection vulnerability in BurtTheCoder mcp-maigret up to version 1.0.12 allows remote attackers to execute arbitrary OS commands via the Username parameter passed to the search_username function in src/index.ts. This is a critical flaw as it enables full remote code execution without authentication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.0.12CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed package versionRun 'npm list mcp-maigret' or check the package.json file for the version fieldAffected if Version is 1.0.12 or lower
-
Verify vulnerable source file existsLocate and inspect src/index.ts in the mcp-maigret installation directory and search for the search_username functionAffected if The file exists and contains the search_username function handling the Username parameter
-
Check if application accepts Username inputReview application logs or configuration to determine if the search_username function is exposed via API, CLI, or MCP interfaceAffected if The function is exposed and accepts user-controlled Username input without sanitization
-
Inspect function implementation for injection pointExamine the search_username function code in src/index.ts for direct use of the Username parameter in OS command execution (e.g., shell exec, spawn)Affected if The Username parameter is passed directly to a command execution method without proper sanitization
You are affected if mcp-maigret version is 1.0.12 or lower and the search_username function is exposed to accept user input.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade mcp-maigret to version 1.0.13 which contains patch b1ae073c4b3e789ab8de36dc6ca8111ae9399e7a. This is a critical severity (CVSS 9.8) vulnerability requiring immediate remediation.
1.0.13
- Check the currently installed version by running: npm list @burtdev/mcp-maigret or npm list mcp-maigret
- Upgrade to version 1.0.13 by running: npm install @burtdev/[email protected] or npm update @burtdev/mcp-maigret
- Verify the upgrade was successful by running: npm list @burtdev/mcp-maigret and confirming version 1.0.13 is installed
- Restart any services or applications that use this package to ensure the patched version is loaded
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2130 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-2130 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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