# CVE-2025-15387: QNO Technology｜VPN Firewall - Insufficient Entropy

> Attackers can brute-force session tokens due to insufficient entropy, allowing them to hijack user sessions and access the VPN Firewall system.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 31 Dec 2025
- **Updated:** 31 Dec 2025
- **Also known as:** GHSA-vvhf-47gr-69vm

## What is CVE-2025-15387?

CVE-2025-15387 is a high-severity vulnerability in QNO Technology VPN Firewall, published on 31 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

VPN Firewall developed by QNO Technology has a Insufficient Entropy vulnerability, allowing unauthenticated remote attackers to obtain any logged-in user session through brute-force attacks and subsequently log into the system.

Weakness: CWE-331 (Insufficient Entropy)

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


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

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

## Is CVE-2025-15387 being exploited?

There is no known exploitation of CVE-2025-15387 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-15387 is a high-severity vulnerability in QNO Technology VPN Firewall, published on 31 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-15387 in the wild and no public exploit code.

Affected product: QNO Technology VPN Firewall. 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-15387/ (Markdown: https://insights.sbomify.com/CVE-2025-15387/index.md)
```

## Sources

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

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