# CVE-2018-25241: VPN Browser+ 1.1.0.0 Denial of Service

> Unauthenticated attackers can crash VPN Browser+ by submitting oversized input to the search bar, causing a denial of service.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Apr 2026
- **Updated:** 6 Apr 2026
- **Also known as:** GHSA-2x95-qpv9-c883

## What is CVE-2018-25241?

CVE-2018-25241 is a high-severity denial of service vulnerability in VPNBrowser VPN Browser+, published on 4 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

VPN Browser+ 1.1.0.0 contains a denial of service vulnerability that allows unauthenticated attackers to crash the application by submitting oversized input through the search functionality. Attackers can paste a large buffer of characters into the search bar to trigger an unhandled exception that terminates the application.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2018-25241?


## How do I fix CVE-2018-25241?

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

## Is CVE-2018-25241 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25241 and fix it if it is affected.

What it is: CVE-2018-25241 is a high-severity denial of service vulnerability in VPNBrowser VPN Browser+, published on 4 Apr 2026. 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-2018-25241 exists.

Affected product: VPNBrowser VPN Browser+. 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-2018-25241/ (Markdown: https://insights.sbomify.com/CVE-2018-25241/index.md)
```

## Sources

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

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