gemini-bridge
Records
1
Disclosed CVEs
1
Exploited (sev 3–4)
0
CISA KEV flagged
0
Newest record 2026-07-31 · 1 distinct CVE id · open in the explorer (the explorer matches the first product a record names, so it can list fewer)
Patch now: confirmed exploitation or KEV · 0
Records at severity 3–4 (exploitation confirmed by CISA, the vendor or reporting) and records flagged as listed in CISA KEV. The KEV flag is the classifier’s cisa-kev tag or a source on the KEV catalog; it is recorded when the collector sees the listing, so a missing flag does not mean a CVE is absent from the catalog.
No record for gemini-bridge has confirmed exploitation or a KEV flag.
Disclosures by month · last 24 months
█
Nov ’241 disclosed · peak 1 in Jul ’26Oct ’26
Disclosed CVEs, no confirmed exploitation · 1
- 2026-07-31CVE-2026-54785CVE-2026-54785: Local file read vulnerability in gemini-bridge MCP server2 Disclosedmcp · local-file-read
This page lists what has been reported, not what to do about it. Versions and fixes are in each linked advisory; check the vendor’s own advisory before acting.