{"answers":{"affected":"3 open source packages ship an affected version, including gemini-bridge.","exploited":"There is no known exploitation of CVE-2026-54785 in the wild and no public exploit code.","fix":"Upgrade gemini-bridge to 1.3.1 or later.","what":"CVE-2026-54785 is a medium-severity path traversal vulnerability in eLyiN gemini-bridge, published on 31 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-54785 and fix it if it is affected.\n\nWhat it is: CVE-2026-54785 is a medium-severity path traversal vulnerability in eLyiN gemini-bridge, published on 31 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-54785 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- gemini-bridge (PyPI): affected from 1.0.0; fixed in 1.3.1\n- gemini-bridge (PyPI): affected from 1.0.0; fixed in 1.3.1\n- gemini-bridge (PyPI): affected from 1.0.0; fixed in 1.3.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-54785/ (Markdown: https://insights.sbomify.com/CVE-2026-54785/index.md)","id":"CVE-2026-54785","markdown":"https://insights.sbomify.com/CVE-2026-54785/index.md","name":"CVE-2026-54785","record":{"aliases":["GHSA-c5px-58j2-7fqp","PYSEC-2026-3574"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Python MCP server","requires_auth":"none","summary":"An attacker can read arbitrary local files by supplying malicious paths to the consult_gemini_with_files function, exposing sensitive data.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.2,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"gemini-bridge vulnerable to arbitrary local file read via consult_gemini_with_files inline mode","id":"CVE-2026-54785","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"Wasmtime: Leak in WASIp1 `fd_renumber` implementation","id":"CVE-2026-54786"},"packages":[{"ecosystem":"PyPI","fixed":["1.3.1"],"introduced":["1.0.0"],"last_affected":[],"package":"gemini-bridge","purl":null,"source":"GHSA-c5px-58j2-7fqp"},{"ecosystem":"PyPI","fixed":["1.3.1"],"introduced":["1.0.0"],"last_affected":[],"package":"gemini-bridge","purl":"pkg:pypi/gemini-bridge","source":"GHSA-c5px-58j2-7fqp"},{"ecosystem":"PyPI","fixed":["1.3.1"],"introduced":["1.0.0"],"last_affected":[],"package":"gemini-bridge","purl":"pkg:pypi/gemini-bridge","source":"PYSEC-2026-3574"}],"prev":{"headline":"CoreWCF: SPNEGO SecurityContextToken proof key wrapped without confidentiality","id":"CVE-2026-54784"},"products":["gemini-bridge"],"published":"2026-07-31","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-03","vendors":["eLyiN"]},"summary":"An attacker can read arbitrary local files by supplying malicious paths to the consult_gemini_with_files function, exposing sensitive data.","url":"https://insights.sbomify.com/CVE-2026-54785/"}