CVE-2026-13500

HIGHPre-NVD 7.37.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.3 from GitHub Security Advisory published 2026-06-28. A secondary CVSS source baseline 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated
7.3EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.3Exploit: No code on recordExposed services: Not assessed

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

The CVE record's description, written by its CNA (VulDB), states the affected versions: "A weakness has been identified in antlr ANTLR4 up to 4.13.2." No release containing a fix is confirmed on record.

A weakness has been identified in antlr ANTLR4 up to 4.13.2. Affected is an unknown function of the file tool/src/org/antlr/v4/codegen/model/OutputFile.java of the component Grammar Action Block Handler. Executing a manipulation can lead to code injection. The attack may be launched remotely. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

CVSS v3
7.3
EG Score
7.3HIGHmedium confidence
EG Risk
64
EG Risk 64/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity73% × 45%
Impact severity (EG Severity): CVSS 7.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.5%
EPSS %ILE
43rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.3): severity, escalated by confirmed exploitation. This CVE's 7.3 is its impact severity (EG Severity), not escalated.

EG Severity
7.3 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 28, 2026

Last Modified

June 29, 2026

Advisory Details (1)

Auto-updated Jun 28, 2026
No fix on record yet.
Web page

antlr4_001_Code_Injection_via_Grammar_Actions · Issue #4 · wooyun123/wooyun · GitHub

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

Vendor Advisories for CVE-2026-13500(1)

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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
antlr44.7.2-5, 4.9.2-1, 4.9.2-2, 4.9.2-3
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
antlr44.7.2-5, 4.9.2-1, 4.9.2-2, 4.9.2-3
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
antlr44.9.2-3
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
antlr44.9.2-3
  • every version on: no fix on record
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 34× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 240 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 140 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  2. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  3. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  4. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  5. 2026-10-18 05:03 UTCEG score recompute
  6. 2026-10-17 18:39 UTCEG score recompute
  7. 2026-10-17 18:38 UTCGHSA enrichmentGHSA-m64j-m5c8-f58p · GitHub CVSS 7.3
  8. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  9. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  10. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  11. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  12. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  13. 2026-10-12 16:35 UTCEG score recompute
  14. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  15. 2026-10-11 20:11 UTCEG score recompute
  16. 2026-10-11 18:23 UTCEG score recompute
  17. 2026-10-11 14:57 UTCEG score recompute
  18. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  19. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  20. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  21. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  22. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  23. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  24. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  25. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.5% · 41st percentile
Show 75 more
  1. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  3. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  4. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  5. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  6. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  7. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  8. 2026-09-23 07:37 UTCEG score recompute
  9. 2026-09-23 07:37 UTCGHSA enrichmentGHSA-m64j-m5c8-f58p · GitHub CVSS 7.3
  10. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  11. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  12. 2026-09-18 07:05 UTCEG score recompute
  13. 2026-09-18 07:05 UTCGHSA enrichmentGHSA-m64j-m5c8-f58p · GitHub CVSS 7.3
  14. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  15. 2026-09-14 00:55 UTCEG score recompute
  16. 2026-09-14 00:55 UTCGHSA enrichmentGHSA-m64j-m5c8-f58p · GitHub CVSS 7.3
  17. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  18. 2026-09-13 09:27 UTCGHSA enrichmentGHSA-m64j-m5c8-f58p · GitHub CVSS 7.3
  19. 2026-09-12 15:18 UTCEG score recompute
  20. 2026-09-12 15:18 UTCGHSA enrichmentGHSA-m64j-m5c8-f58p · GitHub CVSS 7.3
  21. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  22. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  23. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  24. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  25. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  26. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  27. 2026-09-06 14:48 UTCEG score recompute
  28. 2026-09-06 14:48 UTCGHSA enrichmentGHSA-m64j-m5c8-f58p · GitHub CVSS 7.3
  29. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  30. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  31. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  32. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  33. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  34. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  35. 2026-08-30 19:11 UTCEG score recompute
  36. 2026-08-30 19:11 UTCGHSA enrichmentGHSA-m64j-m5c8-f58p · GitHub CVSS 7.3
  37. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  38. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  39. 2026-08-27 22:50 UTCEG score recompute
  40. 2026-08-27 22:50 UTCGHSA enrichmentGHSA-m64j-m5c8-f58p · GitHub CVSS 7.3
  41. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  42. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  43. 2026-08-25 03:52 UTCGHSA enrichmentGHSA-m64j-m5c8-f58p · GitHub CVSS 7.3
  44. 2026-08-24 14:47 UTCEG score recompute
  45. 2026-08-24 14:47 UTCGHSA enrichmentGHSA-m64j-m5c8-f58p · GitHub CVSS 7.3
  46. 2026-08-24 01:39 UTCGHSA enrichmentGHSA-m64j-m5c8-f58p · GitHub CVSS 7.3
  47. 2026-08-23 12:34 UTCEG score recompute
  48. 2026-08-23 12:34 UTCGHSA enrichmentGHSA-m64j-m5c8-f58p · GitHub CVSS 7.3
  49. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  50. 2026-08-22 23:29 UTCGHSA enrichmentGHSA-m64j-m5c8-f58p · GitHub CVSS 7.3
  51. 2026-08-22 10:24 UTCEG score recompute
  52. 2026-08-22 10:24 UTCGHSA enrichmentGHSA-m64j-m5c8-f58p · GitHub CVSS 7.3
  53. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  54. 2026-08-21 21:17 UTCGHSA enrichmentGHSA-m64j-m5c8-f58p · GitHub CVSS 7.3
  55. 2026-08-21 08:10 UTCEG score recompute
  56. 2026-08-21 08:10 UTCGHSA enrichmentGHSA-m64j-m5c8-f58p · GitHub CVSS 7.3
  57. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  58. 2026-08-20 19:04 UTCGHSA enrichmentGHSA-m64j-m5c8-f58p · GitHub CVSS 7.3
  59. 2026-08-20 05:59 UTCEG score recompute
  60. 2026-08-20 05:59 UTCGHSA enrichmentGHSA-m64j-m5c8-f58p · GitHub CVSS 7.3
  61. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  62. 2026-08-19 12:36 UTCGHSA enrichmentGHSA-m64j-m5c8-f58p · GitHub CVSS 7.3
  63. 2026-08-18 23:23 UTCEG score recompute
  64. 2026-08-18 23:23 UTCGHSA enrichmentGHSA-m64j-m5c8-f58p · GitHub CVSS 7.3
  65. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  66. 2026-08-17 17:17 UTCEG score recompute
  67. 2026-08-17 17:17 UTCGHSA enrichmentGHSA-m64j-m5c8-f58p · GitHub CVSS 7.3
  68. 2026-08-17 04:11 UTCGHSA enrichmentGHSA-m64j-m5c8-f58p · GitHub CVSS 7.3
  69. 2026-08-16 15:05 UTCEG score recompute
  70. 2026-08-16 15:05 UTCGHSA enrichmentGHSA-m64j-m5c8-f58p · GitHub CVSS 7.3
  71. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  72. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  73. 2026-08-16 02:00 UTCGHSA enrichmentGHSA-m64j-m5c8-f58p · GitHub CVSS 7.3
  74. 2026-08-15 12:55 UTCEG score recompute
  75. 2026-08-15 12:55 UTCGHSA enrichmentGHSA-m64j-m5c8-f58p · GitHub CVSS 7.3

Frequently asked(5)

What is CVE-2026-13500?
CVE-2026-13500 is a high-severity vulnerability; its CVE record was published on June 28, 2026. A weakness has been identified in antlr ANTLR4 up to 4.13.2. Affected is an unknown function of the file tool/src/org/antlr/v4/codegen/model/OutputFile.java of the component Grammar Action Block Handler. Executing a manipulation can lead to code injection. The attack may be launched remotely. The…
When was the CVE record for CVE-2026-13500 published?
The CVE record for CVE-2026-13500 was published on June 28, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 29, 2026; the record at its source may have been updated since.
Is CVE-2026-13500 actively exploited?
CVE-2026-13500 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-13500?
CVE-2026-13500 has a CVSS base score of 7.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-13500?
No fix for CVE-2026-13500 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's description, written by its CNA (VulDB), states the affected versions: "A weakness has been identified in antlr ANTLR4 up to 4.13.2." No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-13500 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-13500

Explore →

Is Your Infrastructure Affected by CVE-2026-13500?

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