Skip to content
Noroxi
NVD / CVE Program· CNA Go

CVE-2023-24538: Backticks not treated as string delimiters in html/template

Noroxi assessment

Priority: Plan (action score 40/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 2.2% (FIRST EPSS); higher than 83.2% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Go standard library html/template 1.19.8, 1.20.3; azl3 golang 1.19.8-1 on Azure Linux 3.0 1.19.8-1; cbl2 golang 1.17.13-2 on CBL Mariner 2.0 CBL-Mariner Releases.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Add it to your regular patch cycle. Upgrade to Go standard library html/template 1.19.8, 1.20.3; azl3 golang 1.19.8-1 on Azure Linux 3.0 1.19.8-1; cbl2 golang 1.17.13-2 on CBL Mariner 2.0 CBL-Mariner Releases or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Templates do not properly consider backticks (`) as Javascript string delimiters, and do not escape them as expected. Backticks are used, since ES6, for JS template literals. If a template contains a Go template action within a Javascript template literal, the contents of the action can be used to terminate the literal, injecting arbitrary Javascript code into the Go template. As ES6 template literals are rather complex, and themselves can do string interpolation, the decision was made to simply disallow Go template actions from being used inside of them (e.g. "var a = {{.}}"), since there is no obviously safe way to allow this behavior. This takes the same approach as github.com/google/safehtml. With fix, Template.Parse returns an Error when it encounters templates like this, with an ErrorCode of value 12. This ErrorCode is currently unexported, but will be exported in the release of Go 1.21. Users who rely on the previous behavior can re-enable it using the GODEBUG flag jstmpllitinterp=1, with the caveat that backticks will now be escaped. This should be used with caution.

CriticalCVSS 9.8 · v3.1—Proof of concept Fix available
Published
Apr 6, 2023
Updated
Jun 17, 2026
EPSS
2.2% · 83th percentile

Report tools

JSON

Action score

40

Plan

Add it to your regular patch cycle.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-24538

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
golanggo

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • golang gobefore 1.19.8
  • golang go1.20.0 and later · before 1.20.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Go). Independent of NVD's CPE analysis and usually ahead of it.

  • Go standard library html/template

    • before 1.19.8affected · semver
    • 1.20.0-0 and later · before 1.20.3affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8aardvark-dnsbefore 2:1.7.0-1.module_el8.9.0+3657+d86e192f2:1.7.0-1.module_el8.9.0+3657+d86e192f
AlmaLinux:8aardvark-dnsbefore 2:1.0.1-38.module_el8.9.0+3627+db8ec1552:1.0.1-38.module_el8.9.0+3627+db8ec155
AlmaLinux:8buildahbefore 1:1.24.6-7.module_el8.9.0+3627+db8ec1551:1.24.6-7.module_el8.9.0+3627+db8ec155
AlmaLinux:8buildahbefore 1:1.31.3-1.module_el8.9.0+3643+9234dc3b1:1.31.3-1.module_el8.9.0+3643+9234dc3b
AlmaLinux:8buildah-testsbefore 1:1.24.6-7.module_el8.9.0+3627+db8ec1551:1.24.6-7.module_el8.9.0+3627+db8ec155
AlmaLinux:8buildah-testsbefore 1:1.31.3-1.module_el8.9.0+3643+9234dc3b1:1.31.3-1.module_el8.9.0+3643+9234dc3b
AlmaLinux:8cockpit-podmanbefore 75-1.module_el8.9.0+3643+9234dc3b75-1.module_el8.9.0+3643+9234dc3b
AlmaLinux:8cockpit-podmanbefore 46-1.module_el8.7.0+3344+5bcd850f46-1.module_el8.7.0+3344+5bcd850f
AlmaLinux:8conmonbefore 2:2.1.4-2.module_el8.9.0+3627+db8ec1552:2.1.4-2.module_el8.9.0+3627+db8ec155
AlmaLinux:8conmonbefore 3:2.1.8-1.module_el8.9.0+3643+9234dc3b3:2.1.8-1.module_el8.9.0+3643+9234dc3b
AlmaLinux:8container-selinuxbefore 2:2.221.0-1.module_el8.9.0+3643+9234dc3b2:2.221.0-1.module_el8.9.0+3643+9234dc3b
AlmaLinux:8container-selinuxbefore 2:2.205.0-3.module_el8.9.0+3627+db8ec1552:2.205.0-3.module_el8.9.0+3627+db8ec155
AlmaLinux:8containernetworking-pluginsbefore 1:1.3.0-4.module_el8.9.0+3643+9234dc3b1:1.3.0-4.module_el8.9.0+3643+9234dc3b
AlmaLinux:8containernetworking-pluginsbefore 1:1.1.1-5.module_el8.9.0+3627+db8ec1551:1.1.1-5.module_el8.9.0+3627+db8ec155
AlmaLinux:8containers-commonbefore 2:1-38.module_el8.9.0+3627+db8ec1552:1-38.module_el8.9.0+3627+db8ec155
AlmaLinux:8containers-commonbefore 2:1-54.module_el8.9.0+3673+0c64b4032:1-54.module_el8.9.0+3673+0c64b403
AlmaLinux:8critbefore 3.18-4.module_el8.9.0+3643+9234dc3b3.18-4.module_el8.9.0+3643+9234dc3b
AlmaLinux:8critbefore 3.15-3.module_el8.6.0+3137+d33c3efb3.15-3.module_el8.6.0+3137+d33c3efb
AlmaLinux:8critbefore 3.15-3.module_el8.6.0+2877+8e437bf53.15-3.module_el8.6.0+2877+8e437bf5
AlmaLinux:8criubefore 3.18-4.module_el8.9.0+3643+9234dc3b3.18-4.module_el8.9.0+3643+9234dc3b
AlmaLinux:8criubefore 3.15-3.module_el8.6.0+3137+d33c3efb3.15-3.module_el8.6.0+3137+d33c3efb
AlmaLinux:8criubefore 3.15-3.module_el8.6.0+2877+8e437bf53.15-3.module_el8.6.0+2877+8e437bf5
AlmaLinux:8criu-develbefore 3.18-4.module_el8.9.0+3643+9234dc3b3.18-4.module_el8.9.0+3643+9234dc3b
AlmaLinux:8criu-develbefore 3.15-3.module_el8.6.0+2877+8e437bf53.15-3.module_el8.6.0+2877+8e437bf5

+96

Other highest-scoring records for the same primary product.

  • CVE-2018-7187The "go get" implementation in Go 1.9.4, when the -insecure command-line option is used, does not validate the import path (get/vcs.go only
    54Plan
  • CVE-2018-16873In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to remote code execution when executed with the -u flag and
    52Plan
  • CVE-2021-38297Go before 1.16.9 and 1.17.x before 1.17.2 has a Buffer Overflow via large arguments in a function invocation from a WASM module, when GOARCH
    42Plan

Published before and after this one in the same product

  • ← EarlierCVE-2023-24536Apr 6, 2023 · Excessive resource consumption in net/http, net/textproto and mime/multipart
    30Monitor
  • ← EarlierCVE-2023-24537Apr 6, 2023 · Infinite loop in parsing in go/scanner
    30Monitor
  • Later →CVE-2023-24539May 11, 2023 · Improper sanitization of CSS values in html/template
    29Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Go standard library html/template1.19.8Vendor (CNA)
Go standard library html/template1.20.3Vendor (CNA)
azl3 golang 1.19.8-1 on Azure Linux 3.01.19.8-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 golang 1.27.0-1 on Azure Linux 3.0—Microsoft (MSRC)
cbl2 golang 1.17.13-2 on CBL Mariner 2.0CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 golang 1.18.8-7 on CBL Mariner 2.0CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 golang 1.19.8-1 on CBL Mariner 2.01.19.8-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 golang 1.21.6-1 on CBL Mariner 2.01.21.6-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 msft-golang 1.20.11-1 on CBL Mariner 2.01.20.11-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:buildah1:1.31.3-1.el9 · AlmaLinux:9Package registry (OSV)
almalinux:buildah-tests1:1.31.3-1.el9 · AlmaLinux:9Package registry (OSV)
almalinux:containernetworking-plugins1:1.3.0-4.el9 · AlmaLinux:9Package registry (OSV)
almalinux:podman2:4.6.1-5.el9 · AlmaLinux:9Package registry (OSV)
almalinux:podman-docker2:4.6.1-5.el9 · AlmaLinux:9Package registry (OSV)
almalinux:podman-gvproxy2:4.6.1-5.el9 · AlmaLinux:9Package registry (OSV)
almalinux:podman-plugins2:4.6.1-5.el9 · AlmaLinux:9Package registry (OSV)
almalinux:podman-remote2:4.6.1-5.el9 · AlmaLinux:9Package registry (OSV)
almalinux:skopeo2:1.13.3-1.el9 · AlmaLinux:9Package registry (OSV)
almalinux:skopeo-tests2:1.13.3-1.el9 · AlmaLinux:9Package registry (OSV)
almalinux:toolbox0.0.99.4-6.el9_3 · AlmaLinux:9Package registry (OSV)
almalinux:toolbox-tests0.0.99.4-6.el9_3 · AlmaLinux:9Package registry (OSV)
alpine:go1.19.8-r0 · Alpine:v3.17Package registry (OSV)
debian:golang-1.191.19.8-2 · Debian:12Package registry (OSV)
Go:stdlib1.19.8Package registry (OSV)
Go:stdlib1.20.3Package registry (OSV)
opensuse:go1.191.19.8-150000.1.26.1 · openSUSE:Leap 15.4Package registry (OSV)
opensuse:go1.201.20.3-150000.1.8.1 · openSUSE:Leap 15.4Package registry (OSV)
red hat:delve0:1.9.1-1.module+el8.8.0+16778+5fbb74f5 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:delve-debuginfo0:1.9.1-1.module+el8.8.0+16778+5fbb74f5 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:delve-debugsource0:1.9.1-1.module+el8.8.0+16778+5fbb74f5 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)

+23

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×2

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:02023-09-29
Proof-of-concept repository on GitHubstars:02023-09-29

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+175 d
  3. TodayNov 9, 2026+1312 d

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records