Code injection through crafted grammar actions
Published Jun 28, 2026 · Updated Jun 28, 2026
Code injection in ANTLR 4 4.13.0 through 4.13.2 allows remote attackers to embed executable code in generated parsers via grammar actions. The public record identifies OutputFile.java and the grammar action block handler but does not disclose the responsible function or exact unsafe operation. Exploitation requires an attacker-controlled grammar to be processed by the ANTLR tool; the record does not establish a listening service or the context in which injected code executes.
Summary
What happened
Code injection in ANTLR 4 4.13.0 through 4.13.2 allows remote attackers to embed executable code in generated parsers via grammar actions. The public record identifies OutputFile.java and the grammar action block handler but does not disclose the responsible function or exact unsafe operation. Exploitation requires an attacker-controlled grammar to be processed by the ANTLR tool; the record does not establish a listening service or the context in which injected code executes.
The record
- CVE
- CVE-2026-13500
- Published
- Jun 28, 2026
- Updated
- Jun 28, 2026
- Vendor
- ANTLR
- Product
- ANTLR 4
- Classifications
- CWE-94, CWE-74
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 28, 2026CVE publishedPublication date reported by the CVE source.
- Jun 28, 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=4.13.0
- Affected versionversion=4.13.1
- Affected versionversion=4.13.2
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
- antlr4_001_Code_Injection_via_Grammar_Actionsproof 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