# CVE-2018-25368: Nord VPN 6.14.31 Denial of Service via Password Field

> Unauthenticated attackers can crash the NordVPN application by submitting an excessively long string in the password field.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/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:** 25 May 2026
- **Updated:** 26 May 2026
- **Also known as:** GHSA-x9hx-hwff-3m7w

## What is CVE-2018-25368?

CVE-2018-25368 is a high-severity denial of service vulnerability in NordVPN, published on 25 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Nord VPN 6.14.31 contains a denial of service vulnerability that allows unauthenticated attackers to crash the application by submitting an excessively long string in the password field. Attackers can paste a buffer of repeated characters into the password input field to trigger an application crash when attempting to authenticate.

Weakness: CWE-789 (Memory Allocation with Excessive Size Value)

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


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

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

## Is CVE-2018-25368 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-25368 is a high-severity denial of service vulnerability in NordVPN, published on 25 May 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-25368 exists.

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

## Sources

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

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