Advisory record · GHSA-h58c-xccx-75m3

Coder: Stored HTML injection via unescaped ApplicationName and LogoURL appearance settings

CVSS 4.8 MediumEPSS 0.0017 · 6th percentile

Published by the GitHub Advisory Database at 20 Aug 2026, 18:34 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/coder/coder/v2Go>=2.34.0, <2.34.2 || >=2.33.0, <2.33.8 || >=2.30.0, <2.32.7 || <2.29.172.34.2, 2.33.8, 2.32.7, 2.29.17
Identifiers
GHSA-h58c-xccx-75m3 · CVE-2026-111932 · GO-2026-6267
Weakness (CWE)
CWE-74 · CWE-79
Published
20 Aug 2026
Updated
18 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Coder (github.com/coder/coder/v2) versions before 2.29.17, from 2.30.0 before 2.32.7, from 2.33.0 before 2.33.8, and from 2.34.0 before 2.34.2 are affected. The ApplicationName and LogoURL appearance settings were not escaped when rendered, so a user with the Owner role can store HTML that is then shown to other users in the dashboard and in SMTP notification emails. Upgrade to 2.29.17, 2.32.7, 2.33.8, or 2.34.2, matching your release line; until then, restrict the Owner role to trusted administrators.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
4.8 Medium 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.0017, the 6th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 17 Oct 2026, 19:16 UTC Confirmed by NVD
  2. 31 Oct 2026, 14:12 UTC First seen by agentprime
  3. 31 Oct 2026, 14:12 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.