Skip to main content
VulnerabilityPublished Updated

CVE-2026-54785: eLyiN gemini-bridge · Path Traversal

Affects eLyiN gemini-bridgeSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.2 Medium : upgrade to 1.3.1 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
6.2Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.3.1
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade eLyiN gemini-bridge to 1.3.1.

Affected software

ProductAffectedFixed in
eLyiNgemini-bridgeAffected
  • >=1.0.0 <1.3.1
Fixed in
  • 1.3.1
RubyGemsgemini-bridgepkg:gem/gemini-bridgeOther threatsAffected
  • <1.3.1
Fixed in
  • 1.3.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade gemini-bridge to version 1.3.1 or later, where this vulnerability is fixed. No other official remediation or temporary workaround is documented. Patch status is not explicitly stated but the fix is included in version 1.3.1.

Description

gemini-bridge is a lightweight MCP server bridging AI agents to Google's Gemini AI via the official CLI. From 1.0.0 until 1.3.1, 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. This issue is fixed in version 1.3.1.

References

Community reviews

Loading reviews…