Parser panic via unbounded recursive descent
Published Aug 9, 2022 · Updated Mar 6, 2026
Uncontrolled recursion in go/parser before Go 1.17.12 and Go 1.18.4 allows attackers to crash parsing processes with nested source. ParseFile and ParseExprFrom recursively descend through deeply nested types, declarations, statements, and expressions without a depth bound until the call stack is exhausted. The flaw is reachable only when a consuming program parses attacker-controlled Go source, and the resulting panic interrupts that process without reported data exposure or modification.
Summary
What happened
Uncontrolled recursion in go/parser before Go 1.17.12 and Go 1.18.4 allows attackers to crash parsing processes with nested source. ParseFile and ParseExprFrom recursively descend through deeply nested types, declarations, statements, and expressions without a depth bound until the call stack is exhausted. The flaw is reachable only when a consuming program parses attacker-controlled Go source, and the resulting panic interrupts that process without reported data exposure or modification.
The record
- CVE
- CVE-2022-1962
- Published
- Aug 9, 2022
- Updated
- Mar 6, 2026
- Vendor
- Go standard library
- Product
- go/parser
- Classifications
- CWE-674, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 9, 2022CVE publishedPublication date reported by the CVE source.
- Mar 6, 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 <1.17.12
- Affected versionversion=1.18.0-0 <1.18.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.
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