CVE-2026-13501

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory (severity: LOW) published 2026-06-28. a secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 5.3Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A 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.

CVSS v3
5.3
EG Score
5.3(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
49%
KEV
Not listed

Published

June 28, 2026

Last Modified

June 29, 2026

Advisory Details (1)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

antlr4_002_OS_Command_Injection_GoTarget_gofmt · Issue #6 · wooyun123/wooyun · GitHub

https://github.com/wooyun123/wooyun/issues/6

Vendor Advisories for CVE-2026-13501(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 62× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-27 14:13 UTCEPSS rescore
  2. 2026-07-27 12:29 UTCEG score recompute
  3. 2026-07-27 12:29 UTCGHSA enrichment
  4. 2026-07-26 14:54 UTCEPSS rescore
  5. 2026-07-26 14:54 UTCEPSS rescore
  6. 2026-07-26 14:23 UTCEG score recompute
  7. 2026-07-26 14:23 UTCGHSA enrichment
  8. 2026-07-25 14:17 UTCEPSS rescore
  9. 2026-07-24 14:17 UTCEPSS rescore
  10. 2026-07-23 14:18 UTCEPSS rescore
  11. 2026-07-23 03:05 UTCEG score recompute
  12. 2026-07-22 14:08 UTCEPSS rescore
  13. 2026-07-21 15:24 UTCEPSS rescore
  14. 2026-07-20 17:08 UTCEPSS rescore
  15. 2026-07-19 14:30 UTCEPSS rescore
  16. 2026-07-19 02:28 UTCEPSS rescore
  17. 2026-07-18 10:04 UTCEPSS rescore
  18. 2026-07-16 23:59 UTCGHSA enrichment
  19. 2026-07-16 17:02 UTCEPSS rescore
  20. 2026-07-16 01:58 UTCGHSA enrichment
  21. 2026-07-15 16:57 UTCEPSS rescore
  22. 2026-07-15 03:57 UTCGHSA enrichment
  23. 2026-07-15 02:00 UTCEPSS rescore
  24. 2026-07-14 05:55 UTCGHSA enrichment
  25. 2026-07-13 22:30 UTCEPSS rescore
Show 37 more
  1. 2026-07-13 07:53 UTCGHSA enrichment
  2. 2026-07-13 06:12 UTCEPSS rescore
  3. 2026-07-12 09:51 UTCGHSA enrichment
  4. 2026-07-12 05:46 UTCEPSS rescore
  5. 2026-07-11 11:49 UTCGHSA enrichment
  6. 2026-07-11 08:27 UTCEPSS rescore
  7. 2026-07-10 13:48 UTCGHSA enrichment
  8. 2026-07-09 19:10 UTCEPSS rescore
  9. 2026-07-09 15:43 UTCGHSA enrichment
  10. 2026-07-08 17:40 UTCGHSA enrichment
  11. 2026-07-08 15:15 UTCEPSS rescore
  12. 2026-07-08 15:15 UTCEPSS rescore
  13. 2026-07-07 19:39 UTCGHSA enrichment
  14. 2026-07-07 13:46 UTCEPSS rescore
  15. 2026-07-06 21:37 UTCGHSA enrichment
  16. 2026-07-06 16:27 UTCEPSS rescore
  17. 2026-07-06 02:23 UTCEPSS rescore
  18. 2026-07-05 23:36 UTCGHSA enrichment
  19. 2026-07-05 02:30 UTCEPSS rescore
  20. 2026-07-05 02:30 UTCEPSS rescore
  21. 2026-07-05 01:34 UTCGHSA enrichment
  22. 2026-07-04 06:31 UTCEPSS rescore
  23. 2026-07-04 03:31 UTCGHSA enrichment
  24. 2026-07-03 05:29 UTCGHSA enrichment
  25. 2026-07-02 07:20 UTCGHSA enrichment
  26. 2026-07-01 15:06 UTCEPSS rescore
  27. 2026-07-01 15:06 UTCEPSS rescore
  28. 2026-07-01 09:18 UTCGHSA enrichment
  29. 2026-06-30 23:22 UTCEPSS rescore
  30. 2026-06-30 11:16 UTCGHSA enrichment
  31. 2026-06-29 17:26 UTCNVD updateCVSS v4 → 1.9
  32. 2026-06-29 16:13 UTCMITRE cvelistV5CVSS v4 → 4.8
  33. 2026-06-29 14:06 UTCEPSS rescore
  34. 2026-06-29 13:10 UTCGHSA enrichment
  35. 2026-06-28 16:02 UTCNVD updateCVSS v4 → 1.9
  36. 2026-06-28 15:08 UTCEG score recompute
  37. 2026-06-28 15:07 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-13501?
CVE-2026-13501 is a medium vulnerability published on June 28, 2026. A 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…
When was CVE-2026-13501 disclosed?
CVE-2026-13501 was first published in the National Vulnerability Database on June 28, 2026, with the most recent update on June 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-13501 actively exploited?
CVE-2026-13501 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 51.4% of all scored CVEs.
What is the CVSS score of CVE-2026-13501?
CVE-2026-13501 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-13501?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-13501, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-13501

Explore →

Is Your Infrastructure Affected by CVE-2026-13501?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs