gemini-bridge vulnerable to arbitrary local file read via consult_gemini_with_files inline mode

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.2 · CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2026-54785: 0.19% estimated exploitation activity in the next 30 days; percentile 8.82 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary consultgeminiwithfiles 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: consultgeminiwithfiles(query, directory, files, …), mode="inline" - Sink: readfileforinline via prepareinlinepayload in src/mcpserver.py - The atcommand mode already confined paths; inline mode did not. Root cause resolvepath returned an out-of-root path while only nullifying the display name, and prepareinlinepayload read the file regardless. Absolute…

Published by the source

31 Jul 2026, 22:31 UTC

Last modified by the source

31 Jul 2026, 22:31 UTC

Source last checked

26 Oct 2026, 13:50 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-c5px-58j2-7fqp

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-54785

Advisory: gemini-bridge vulnerable to arbitrary local file read via consult_gemini_with_files inline mode
IDs: CVE-2026-54785, GHSA-c5px-58j2-7fqp
Record: https://patchnext.com/advisories/cve-2026-54785 (revision 1, source checked 26 Oct 2026, 13:50 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: gemini-bridge 1.3.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI gemini-bridge: affected >= 1.0.0, < 1.3.1; fixed in 1.3.1

## Suggested inspection (read-only)
- `python -m pip show gemini-bridge`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on gemini-bridge.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-c5px-58j2-7fqp (GitHub-reviewed advisory GHSA-c5px-58j2-7fqp lists affected ranges: PyPI gemini-bridge >=1.0.0 <1.3.1)

Commands are suggestions: review each one before running it.