Assembler crash via unchecked GROUP directive
Published Apr 10, 2026 · Updated Apr 10, 2026
Heap buffer overflow in NASM 3.02rc5 allows local users to corrupt heap memory and crash the assembler through a crafted assembly file. In output/outobj.c, obj_directive() processes a GROUP directive without checking bounds before writing to a heap buffer. A user or build process must assemble attacker-controlled source; the published proof of concept demonstrates the crash path, while code execution is not publicly demonstrated.
Summary
What happened
Heap buffer overflow in NASM 3.02rc5 allows local users to corrupt heap memory and crash the assembler through a crafted assembly file. In output/outobj.c, obj_directive() processes a GROUP directive without checking bounds before writing to a heap buffer. A user or build process must assemble attacker-controlled source; the published proof of concept demonstrates the crash path, while code execution is not publicly demonstrated.
The record
- CVE
- CVE-2026-6067
- Published
- Apr 10, 2026
- Updated
- Apr 10, 2026
- Vendor
- NASM
- Product
- NASM
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 10, 2026CVE publishedPublication date reported by the CVE source.
- Apr 10, 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=nasm-3.02rc5
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
- poc_nasm_group_oob.pyproof of concept · unverified
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