# CVE-2019-25365: ChaosPro 2.0 - Buffer Overflow

> Attackers can execute arbitrary code on Windows XP systems by crafting a malicious configuration file that triggers a buffer overflow in ChaosPro.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Feb 2026
- **Updated:** 19 Feb 2026
- **Also known as:** GHSA-p5wr-fv9m-v746

## What is CVE-2019-25365?

CVE-2019-25365 is a high-severity memory corruption vulnerability in ChaosPro, published on 18 Feb 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

ChaosPro 2.0 contains a buffer overflow vulnerability in the configuration file path handling that allows attackers to execute arbitrary code by overwriting the Structured Exception Handler. Attackers can craft a malicious configuration file with carefully constructed payload to overwrite memory and gain remote code execution on vulnerable Windows XP systems.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2019-25365?


## How do I fix CVE-2019-25365?

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

## Is CVE-2019-25365 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25365 and fix it if it is affected.

What it is: CVE-2019-25365 is a high-severity memory corruption vulnerability in ChaosPro, published on 18 Feb 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-2019-25365 exists.

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

## Sources

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

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