Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The gemini-bridge package versions 1.0.0 up to but not including 1.3.1 are vulnerable. In inline mode of consult_gemini_with_files, files passed in the files argument were read without being confined to the working directory, so a caller (including an LLM that was prompt-injected) can read any file the server can access and receive its contents in the tool response. Upgrade to gemini-bridge 1.3.1, or avoid inline mode with untrusted files input until then.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 6.2 | Medium | 3.1 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0019, the 8th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:41 UTC First seen by agentprime
- 31 Oct 2026, 14:41 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-c5px-58j2-7fqp
- OSV: GHSA-c5px-58j2-7fqp
- github.com/eLyiN/gemini-bridge/security/advisories/GHSA-c5px-58j2-7fqp
- github.com/eLyiN/gemini-bridge/pull/9
- github.com/eLyiN/gemini-bridge/commit/8f3b85afd02b692c4bc974b5176e12fb277ea801
- github.com/eLyiN/gemini-bridge
- github.com/eLyiN/gemini-bridge/releases/tag/v1.3.1