CVE-2026-13501
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA security vulnerability has been detected in antlr ANTLR4 up to 4.13.2. Affected by this vulnerability is the function GoTarget of the file tool/src/org/antlr/v4/codegen/target/GoTarget.java of the component gofmt. The manipulation leads to command injection. The attack can only be performed from a local environment. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCommand injection vulnerability in ANTLR4's Go code generation target (GoTarget.java) within the gofmt functionality. The GoTarget function does not properly sanitize input before passing it to system command execution, allowing a local attacker to inject arbitrary commands.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify ANTLR4 installationSearch for ANTLR4 libraries (antlr4-*.jar) in the system, project dependencies (Maven pom.xml, Gradle build.gradle, or similar), or check if ANTLR is imported in any Java project files.Affected if ANTLR4 is present in the environment and is used for code generation.
-
Verify Go code generation target is in useSearch project build configurations (build files, code generation scripts) for references to 'Go', 'GoTarget', or '-Dlanguage=Go' as a code generation target.Affected if The Go code generation target is enabled or referenced in any build or generation process.
-
Check ANTLR4 versionInspect the installed ANTLR4 JAR file name, Maven/Gradle dependency declaration, or run 'java -jar antlr-*-complete.jar -version' to obtain the version number.Affected if The installed version is unknown, unpatched, or older than any official fix release.
-
Inspect GoTarget.java usageSearch for imports or references to 'org.antlr.mojo.golang.GoTarget' or 'GoTarget' class in the codebase, and examine any Java source files that instantiate or call methods on this class.Affected if Code directly invokes GoTarget functionality, particularly around gofmt operations.
-
Audit input to gofmt operationsReview how user-controlled input (file paths, filenames, user parameters) flows into ANTLR's Go code generation process, particularly before gofmt is invoked.Affected if Untrusted or unsanitized input can reach the GoTarget gofmt execution pathway.
A user is affected if ANTLR4 is present, the Go code generation target is used, and unpatched ANTLR4 version is running with unsanitized input reaching GoTarget gofmt operations.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataAvoid using the Go code generation target until official patch is available; implement strict input validation/sanitization on any user-controlled input before passing to GoTarget functions, particularly around gofmt operations.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13501 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-13501 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data