# CVE-2019-25691: Faleemi Desktop Software 1.8 Local Buffer Overflow SEH DEP Bypass

> Local attackers can execute arbitrary code by triggering a buffer overflow in the System Setup dialog, bypassing DEP protections via SEH exploitation.

- **Severity:** High 8.6 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 12 Apr 2026
- **Updated:** 13 Apr 2026
- **Also known as:** GHSA-w77h-76xc-792q

## What is CVE-2019-25691?

CVE-2019-25691 is a high-severity memory corruption vulnerability in Faleemi Desktop Software, published on 12 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Faleemi Desktop Software 1.8 contains a local buffer overflow vulnerability in the System Setup dialog that allows attackers to bypass DEP protections through structured exception handling exploitation. Attackers can inject a crafted payload into the Save Path for Snapshot and Record file field to trigger a buffer overflow and execute arbitrary code via ROP chain gadgets.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

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

## Is CVE-2019-25691 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-25691 is a high-severity memory corruption vulnerability in Faleemi Desktop Software, published on 12 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25691 exists.

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

## Sources

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

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