# CVE-2026-45182: Information disclosure in GrapheneOS

> Attackers can discover the real IP address of VPN users on GrapheneOS when specific VPN settings are enabled, compromising user privacy.

- **Severity:** Low 2.2 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 May 2026
- **Updated:** 11 May 2026
- **Also known as:** GHSA-47rq-88xv-gpxv

## What is CVE-2026-45182?

CVE-2026-45182 is a low-severity vulnerability in GrapheneOS, published on 9 May 2026. 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

GrapheneOS before 2026050400 allows attackers to discover the real IP address of a VPN user as a consequence of a registerQuicConnectionClosePayload optimization, because an application can let system_server transmit UDP traffic on its behalf. This occurs when the "Block connections without VPN" and "Always-on VPN" settings are enabled.

Weakness: CWE-441 (Unintended Proxy or Intermediary)

## Which versions are affected by CVE-2026-45182?


## How do I fix CVE-2026-45182?

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

## Is CVE-2026-45182 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-45182 and fix it if it is affected.

What it is: CVE-2026-45182 is a low-severity vulnerability in GrapheneOS, published on 9 May 2026. 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-2026-45182 exists.

Affected product: GrapheneOS. 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-2026-45182/ (Markdown: https://insights.sbomify.com/CVE-2026-45182/index.md)
```

## Sources

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

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