Vulnerability in code-index-mcp (CVE-2026-10692)
Summary
Vulnerability in code-index-mcp (CVE-2026-10692). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.14.1 or later.
Original description
The description as published by the source.
A weakness has been identified in johnhuang316 code-index-mcp up to 2.14.0. Affected is the function is_safe_regex_pattern of the component search_code_advanced. Executing a manipulation of the argument regex can lead to inefficient regular expression complexity. It is possible to launch the attack remotely. The exploit has been made available to the public and could be used for attacks. Upgrading to version 2.14.1 is able to address this issue. This patch is called 25bc02fac74051ddae15ce79e952f00211b1ea6b. Upgrading the affected component is recommended.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-10692 has been found in code-index-mcp.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade code-index-mcp to 2.14.1 or later.
If unsure, ask your IT team or search "code-index-mcp CVE-2026-10692" on the vendor's site.
CVE-2026-10692 (code-index-mcp) — CWE-400 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 2.14.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-400) exists in code-index-mcp.
Check the vendor advisory for the affected versions of code-index-mcp.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 2.14.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'code-index-mcp' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'code-index-mcp' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
code-index-mcpを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade code-index-mcp to 2.14.1ステージング環境で 2.14.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory vuldb.com
- advisory vuldb.com
- advisory vuldb.com
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- report github.com
- report vuldb.com
- web github.com
- web github.com