Information Disclosure in gemini-bridge (CVE-2026-54785)
Summary
Vulnerability in gemini-bridge (CVE-2026-54785). Confidential information can be exposed externally. Exploitable via consult_gemini_with_files. Mitigation: upgrade to 1.3.1 or later.
Original description
The description as published by the source.
Summary
consult_gemini_with_files in inline mode read any file path supplied in
the files argument without confining it to the working directory, then
forwarded the contents to the Gemini CLI. Because the caller also controls
query, the file contents are echoed back through the Gemini round-trip
(and sent to Google), making this an arbitrary local file read.
Impact
An MCP client — or an LLM that has been prompt-injected into calling the tool —
can read any file the server process can access (SSH keys, cloud
credentials, .env, source) and have it disclosed via the tool response.
No code execution by itself.
Affected component
- Tool:
consult_gemini_with_files(query, directory, files, …),mode="inline" - Sink:
_read_file_for_inlinevia_prepare_inline_payloadinsrc/mcp_server.py - The
at_commandmode already confined paths; inline mode did not.
Root cause
_resolve_path returned an out-of-root path while only nullifying the display
name, and _prepare_inline_payload read the file regardless. Absolute paths,
.. traversal, and symlink escapes were all accepted.
Patch
Fixed in 1.3.1. _resolve_path now resolves symlinks and confines via
Path.relative_to(root); inline mode skips any entry that resolves outside the
working directory (the same guard at_command already enforced).
Workarounds
Upgrade to 1.3.1. Before upgrading, avoid mode="inline" with untrusted
files input, or run the server with a restrict…
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-54785 has been found in gemini-bridge.
Attackers can target a specific entry point like consult_gemini_with_files over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.2/10.
What to do: upgrade gemini-bridge to 1.3.1 or later.
If unsure, ask your IT team or search "gemini-bridge CVE-2026-54785" on the vendor's site.
CVE-2026-54785 (gemini-bridge) — CWE-200 / CVSS v3 6.2
Attack vector: local / unauthenticated / no user interaction
Attack surface: consult_gemini_with_files / files / directory / query
Patched: 1.3.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.
Information disclosure (CWE-200) exists in gemini-bridge. Attackers reach the vulnerable code path via consult_gemini_with_files without authentication.
Check the vendor advisory for the affected versions of gemini-bridge. Attack surface: consult_gemini_with_files / files / directory / query.
Severity: Medium (CVSS 6.2/10). Confidential information can be exposed externally.
Update to 1.3.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 'gemini-bridge' . 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 'gemini-bridge' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
gemini-bridgeを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade gemini-bridge to 1.3.1ステージング環境で 1.3.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- package pypi.org
- web github.com
- web github.com
- web github.com
- web github.com