Compiler crash or code execution via unchecked mangling
Published Mar 26, 2026 · Updated Mar 26, 2026
Stack-based buffer overflow in Zen C before 0.4.4 allows attackers to crash the compiler via crafted source-file identifiers. Name-mangling paths use sprintf and strcat to copy unbounded struct, trait, method, and generic names into fixed-size stack buffers. Processing an untrusted .zc file is required; a crash is demonstrated, while code execution is not demonstrated and would inherit the compiler process's privileges.
Summary
What happened
Stack-based buffer overflow in Zen C before 0.4.4 allows attackers to crash the compiler via crafted source-file identifiers. Name-mangling paths use sprintf and strcat to copy unbounded struct, trait, method, and generic names into fixed-size stack buffers. Processing an untrusted .zc file is required; a crash is demonstrated, while code execution is not demonstrated and would inherit the compiler process's privileges.
The record
- CVE
- CVE-2026-33491
- Published
- Mar 26, 2026
- Updated
- Mar 26, 2026
- Vendor
- Zen C
- Product
- Zen C
- Classifications
- CWE-121, CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 26, 2026CVE publishedPublication date reported by the CVE source.
- Mar 26, 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=< 0.4.4
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
- Zen C long-identifier ASan reproductionproof 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