# CVE-2025-5009: Information Disclosure in Gemini iOS App

> Sharing a snippet in the Gemini iOS app inadvertently exposed the entire conversation history via a public link, allowing unauthorized data access.

- **Severity:** Low 1.0 (`CVSS:4.0/AV:A/AC:L/AT:P/PR:H/UI:A/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Oct 2025
- **Updated:** 22 Jan 2026
- **Also known as:** GHSA-95r2-976x-qjfh

## What is CVE-2025-5009?

CVE-2025-5009 is a low-severity vulnerability in Google Gemini, published on 8 Oct 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

In Gemini iOS, when a user shared a snippet of a conversation, it would share the entire conversation via a sharable public link that contained the entire conversation history and not just the snippet.

Weakness: CWE-359 (Exposure of Private Personal Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-5009?


## How do I fix CVE-2025-5009?

No fix has been published for CVE-2025-5009 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-5009 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5009 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-5009 and fix it if it is affected.

What it is: CVE-2025-5009 is a low-severity vulnerability in Google Gemini, published on 8 Oct 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5009 exists.

Affected product: Google Gemini. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-5009/ (Markdown: https://insights.sbomify.com/CVE-2025-5009/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-5009
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-5009
- OSV: https://osv.dev/vulnerability/CVE-2025-5009

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-5009/
Summaries are generated and may contain mistakes; the official description above is the record.