CVE-2026-97030
published 2026-10-08CVE-2026-97030: A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped. We now ensure…
PriorityP426medium6.1CVSS 3.1
AVNACLPRNUIRSCCLILAN
EPSS
0.20%
9.6th percentile
A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped. We now ensure that valid keyword uses are escaped and non-keyword uses are not escaped.
Affected
2 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| go_standard_library | html_template | < 1.26.9 | 1.26.9 |
| go_standard_library | html_template | >= 1.27.0-0 < 1.27.2 | 1.27.2 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
VulDB
Go html/template up to 1.26.8/1.27.1 Template cross site scripting (EUVD-2026-95416)
vuldb·2026-10-09
CVE-2026-97030 [LOW] Go html/template up to 1.26.8/1.27.1 Template cross site scripting (EUVD-2026-95416)
A vulnerability marked as problematic has been reported in Go html and template up to 1.26.8/1.27.1. This impacts an unknown function of the component Template. This manipulation causes cross site scripting.
The identification of this vulnerability is CVE-2026-97030. It is possible to initiate the attack remotely. There is no exploit available.
It is suggested to upgrade the affected component.
GHSA
A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped.
ghsa_unreviewed·2026-10-09
CVE-2026-97030 A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped.
A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped. We now ensure that valid keyword uses are escaped and non-keyword uses are not escaped.
No detection rules found.
No public exploits indexed.
2026-10-08
Published