# CVE-2025-49850: Out-of-bounds Read in Write in LS Electric GMWin 4

> Heap-based buffer overflow in LS Electric GMWin 4 allows attackers to execute arbitrary code or cause denial of service via malicious PRJ files.

- **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:** 17 Jun 2025
- **Updated:** 17 Jun 2025
- **Also known as:** GHSA-vgp9-qcv2-338w

## What is CVE-2025-49850?

CVE-2025-49850 is a high-severity memory corruption vulnerability in LS Electric GMWin 4, published on 17 Jun 2025. 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

A Heap-based Buffer Overflow vulnerability exists within the parsing of PRJ files. The issues result from the lack of proper validation of user-supplied data, which can result in different memory corruption issues within the application, such as reading and writing past the end of allocated data structures.

Weakness: CWE-122 (Heap-based Buffer Overflow)

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


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

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

## Is CVE-2025-49850 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-49850 is a high-severity memory corruption vulnerability in LS Electric GMWin 4, published on 17 Jun 2025. 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: There is no known exploitation of CVE-2025-49850 in the wild and no public exploit code.

Affected product: LS Electric GMWin 4. 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-49850/ (Markdown: https://insights.sbomify.com/CVE-2025-49850/index.md)
```

## Sources

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

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