Assembler crash via out-of-bounds parser read
Published Aug 11, 2025 · Updated Aug 11, 2025
Stack-based buffer overflow in NASM 2.17rc0 allows local users to crash the assembler by processing a malformed assembly file. The parse_line function in asm/parser.c reads eight bytes beyond the stack object named dummy after insufficiently bounded parsing of unexpected syntax. Exploitation requires permission to invoke NASM on attacker-controlled source; the demonstrated consequence is an AddressSanitizer abort and process crash, not proven code execution.
Summary
What happened
Stack-based buffer overflow in NASM 2.17rc0 allows local users to crash the assembler by processing a malformed assembly file. The parse_line function in asm/parser.c reads eight bytes beyond the stack object named dummy after insufficiently bounded parsing of unexpected syntax. Exploitation requires permission to invoke NASM on attacker-controlled source; the demonstrated consequence is an AddressSanitizer abort and process crash, not proven code execution.
The record
- CVE
- CVE-2025-8846
- Published
- Aug 11, 2025
- Updated
- Aug 11, 2025
- Vendor
- NASM
- Product
- NASM
- Classifications
- CWE-121, CWE-119
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 11, 2025CVE publishedPublication date reported by the CVE source.
- Aug 11, 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=2.17rc0
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
- POC_nasm_stack_buffer_overflow_parse_lineproof of concept · 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