Local process crash via menu-language buffer overflow
Published Mar 11, 2026 · Updated Mar 11, 2026
Buffer overflow in R 3.4.4 for Windows x64 allows local users to crash the process through the GUI menu-language preference. The field processes an 8,000-byte value without enforcing its buffer boundary, overwriting the SEH record after 1,016 bytes and pivoting into a ROP chain. Local GUI access is required, and the CNA's scored impact is limited to loss of availability despite the public exploit's shellcode payload.
Summary
What happened
Buffer overflow in R 3.4.4 for Windows x64 allows local users to crash the process through the GUI menu-language preference. The field processes an 8,000-byte value without enforcing its buffer boundary, overwriting the SEH record after 1,016 bytes and pivoting into a ROP chain. Local GUI access is required, and the CNA's scored impact is limited to loss of availability despite the public exploit's shellcode payload.
The record
- CVE
- CVE-2019-25485
- Published
- Mar 11, 2026
- Updated
- Mar 11, 2026
- Vendor
- R Foundation for Statistical Computing
- Product
- R
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 11, 2026CVE publishedPublication date reported by the CVE source.
- Mar 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.4.4
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- R 3.4.4 Windows 10 x64 Buffer Overflow SEH DEP/ASLR Bypassfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo