CVE-2023-24538

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2023-04-06. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2023-28554 (ENISA EUVD) · GHSA-v4m2-x4rp-hv22 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2.3%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
45
EG Risk 45/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation2.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
2.3%
EPSS %ILE
83rd
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
2.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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

April 6, 2023

Last Modified

February 12, 2025

Advisory Details (5)

Auto-updated Oct 10, 2026
Patch available.
Web page

Go: Multiple Vulnerabilities (GLSA 202311-09) — Gentoo security

https://security.gentoo.org/glsa/202311-09
Web page

GO-2023-1703 - Go Packages

https://pkg.go.dev/vuln/GO-2023-1703
Web page
https://groups.google.com/g/golang-announce/c/Xdv6JL9ENs8
Web page

html/template: backticks not treated as string delimiters (CVE-2023-24538) · Issue #59234 · golang/go · GitHub

https://go.dev/issue/59234
Web page
https://go.dev/cl/482079

Vendor Advisories for CVE-2023-24538(20)

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

Patch Availability(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatamq7/amq-broker-rhel8-operator-bundle:7.12.0-102024-05-21redhat
redhatrhceph/rhceph-5-dashboard-rhel8:5-832024-02-08redhat
redhatcontainer-tools:4.0-8090020230828093056.e7857ab12023-11-14redhat
redhatcontainer-tools:rhel8-8090020230825121312.e7857ab12023-11-14redhat
redhatbuildah-1:1.31.3-1.el92023-11-07redhat
redhatskopeo-2:1.13.3-1.el92023-11-07redhat
redhatpodman-2:4.6.1-5.el92023-11-07redhat
redhatcontainernetworking-plugins-1:1.3.0-4.el92023-11-07redhat
redhattoolbox-0:0.0.99.4-6.el9_32023-11-07redhat
redhatmigration-toolkit-virtualization/mtv-controller-rhel9:2.4.3-52023-10-25redhat
redhatcollectd-libpod-stats-0:1.0.4-5.el8ost2023-10-20redhat
redhatopenshift-secondary-scheduler-operator/secondary-scheduler-operator-rhel8:v1.1-302023-08-23redhat
redhatcontainer-native-virtualization/kubevirt-template-validator-rhel9:v4.13.3-62023-08-16redhat
redhatmta/mta-hub-rhel9:6.2.0-162023-08-14redhat
redhatquay/quay-rhel8:v3.8.11-132023-08-10redhat
redhatjetstack-cert-manager-container-v1.10.2-182023-08-08redhat
redhatopenshift-clients-0:4.12.0-202307200611.p0.g49844f7.assembly.stream.el82023-08-03redhat
redhatopenshift-clients-0:4.13.0-202306230038.p0.ge4c9a6a.assembly.stream.el82023-07-20redhat
redhatskupper-cli-0:1.4.1-2.el92023-07-10redhat
redhatadvanced-cluster-security/rhacs-main-rhel8:4.1.0-132023-06-29redhat
redhatoadp/oadp-velero-rhel8:1.1.5-32023-06-29redhat
redhatconmon-3:2.1.7-2.1.rhaos4.13.el92023-06-23redhat
redhatcontainer-native-virtualization/vm-network-latency-checkup-rhel9:v4.13.1-32023-06-20redhat
redhatrhmtc/openshift-velero-plugin-rhel8:v1.7.10-22023-06-15redhat
redhatopenshift-clients-0:4.13.0-202305312300.p0.g05d83ef.assembly.stream.el82023-06-13redhat
redhatmicroshift-0:4.13.3-202306081201.p0.g16708cc.assembly.4.13.3.el92023-06-13redhat
redhatopenshift4/ovirt-csi-driver-rhel8-operator:v4.13.0-202305262054.p0.g3e49f77.assembly.stream2023-06-07redhat
redhatskopeo-2:1.11.2-1.1.rhaos4.13.el92023-06-07redhat
redhatopenshift-serverless-clients-0:1.8.1-3.el82023-06-05redhat
redhatetcd-0:3.3.23-14.el8ost2023-06-05redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
golang-1.151.15.15-1 ... 1.15.9-6 (10 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
golang-1.19—
  • every version up to 1.19.8-2: fixed in 1.19.8-2
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
stdlib—
  • every version up to 1.19.8: fixed in 1.19.8
  • 1.20.0-0 up to 1.20.3: fixed in 1.20.3
—

Weakness Classification(1)

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

Additional Vendor Advisories

(16)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 28× in last 7d / 95× 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 277 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 177 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2023-24538?
CVE-2023-24538 is a critical-severity vulnerability; its CVE record was published on April 6, 2023. 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…
When was the CVE record for CVE-2023-24538 published?
The CVE record for CVE-2023-24538 was published on April 6, 2023. 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 February 12, 2025; the record at its source may have been updated since.
Is CVE-2023-24538 actively exploited?
CVE-2023-24538 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.3% probability of exploitation in the next 30 days (83rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-24538?
CVE-2023-24538 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2023-24538?
A fix for CVE-2023-24538 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-24538 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-2023-24538

Explore →

Is Your Infrastructure Affected by CVE-2023-24538?

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

Book a Demo →Browse All CVEs