# CVE-2025-59692: Misconfiguration in PureVPN

> PureVPN Linux client flushes existing firewall rules and fails to restore them, potentially exposing the system to unauthorized network traffic.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Sep 2025
- **Updated:** 19 Sep 2025
- **Also known as:** GHSA-f3jf-wgcf-hqjr, ROOT-OS-UBUNTU-2204-CVE-2025-59692

## What is CVE-2025-59692?

CVE-2025-59692 is a low-severity vulnerability in PureVPN, published on 18 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PureVPN client applications on Linux through September 2025 mishandle firewalling. They flush the system's existing iptables rules and apply default ACCEPT policies when connecting to a VPN server. This removes firewall rules that may have been configured manually or by other software (e.g., UFW, container engines, or system security policies). Upon VPN disconnect, the original firewall state is not restored. As a result, the system may become unintentionally exposed to network traffic that was previously blocked. This affects CLI 2.0.1 and GUI 2.10.0.

Weakness: CWE-669 (Incorrect Resource Transfer Between Spheres)

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


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

No fix published yet.

## Is CVE-2025-59692 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-59692 is a low-severity vulnerability in PureVPN, published on 18 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-59692 exists.

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

## Sources

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

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