Memory corruption via unbalanced Lua error stack
Published Jun 23, 2025 · Updated Jun 23, 2025
Out-of-bounds write in Notepad Next 0 through 0.11 allows local users to corrupt process memory through embedded Lua error handling. The luaG_runerror path retains the original message after luaG_addinfo pushes an annotated replacement, while luaV_concat adjusts L->top against a changed stack. The public record does not identify the triggering document or script, and the established consequence is memory corruption rather than code execution.
Summary
What happened
Out-of-bounds write in Notepad Next 0 through 0.11 allows local users to corrupt process memory through embedded Lua error handling. The luaG_runerror path retains the original message after luaG_addinfo pushes an annotated replacement, while luaV_concat adjusts L->top against a changed stack. The public record does not identify the triggering document or script, and the established consequence is memory corruption rather than code execution.
The record
- CVE
- CVE-2025-52939
- Published
- Jun 23, 2025
- Updated
- Jun 23, 2025
- Vendor
- dail8859
- Product
- Notepad Next
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 23, 2025CVE publishedPublication date reported by the CVE source.
- Jun 23, 2025Record 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=0 <=v0.11
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
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