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)
Exploited or KEV-listed · 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
█
Dec ’241 disclosed · peak 1 in Jul ’26Nov ’26
Disclosed CVEs, no confirmed exploitation · 1
- closed6.2gemini-bridge CVE-2026-54785: Local file read vulnerability in gemini-bridge MCP server
Disclosed · since 31 Jul 2026 · CVE-2026-54785
AI
Fix status and fixed versions are recorded when a source states them (each record’s page shows what is known); check the vendor’s own advisory before acting.