# CVE-2019-25485: R 3.4.4 Windows x64 Buffer Overflow SEH DEP ASLR Bypass

> Local attackers can execute arbitrary code by exploiting a buffer overflow in the R GUI language menu, bypassing DEP and ASLR protections.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/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:** 11 Mar 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-48cq-3q6q-vxm7

## What is CVE-2019-25485?

CVE-2019-25485 is a medium-severity memory corruption vulnerability in R-Project R, published on 11 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

R 3.4.4 on Windows x64 contains a buffer overflow vulnerability in the GUI Preferences language menu field that allows local attackers to bypass DEP and ASLR protections. Attackers can inject a crafted payload through the Language for menus preference to trigger a structured exception handler chain pivot and execute arbitrary shellcode with application privileges.

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

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


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

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

## Is CVE-2019-25485 being exploited?

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

Public exploit code:

- Stack-based buffer overflow in R 3.4.4. Full exploitation on x86, but only RIP control with gadget analysis on x64 due to program constraints. The same vulnerability across two architectures, leading to different exploitation paths. (github_poc): https://github.com/TheMalwareGuardian/CVE-2019-25485

## Fix prompt for AI coding agents

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

What it is: CVE-2019-25485 is a medium-severity memory corruption vulnerability in R-Project R, published on 11 Mar 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-25485 exists.

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

## Sources

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

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