Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-111932 Overview
CVE-2026-111932 is a stored HTML injection vulnerability in Coder, an open-source platform for provisioning remote development environments. The flaw exists because the ApplicationName and LogoURL appearance settings are rendered into HTML output without sufficient escaping [CWE-79]. An attacker with the Owner role can store HTML markup in these settings that renders in the Coder dashboard and in SMTP notification emails sent to other deployment users. The issue affects Coder versions prior to 2.29.17, 2.30.0 before 2.32.7, 2.33.0 before 2.33.8, and 2.34.0 before 2.34.2.
Critical Impact
Owner-level attackers can inject persistent HTML into dashboard pages and outbound notification emails, enabling phishing and brand-abuse attacks against other users of the Coder deployment.
Affected Products
- Coder versions prior to 2.29.17
- Coder versions 2.30.0 through 2.32.6 and 2.33.0 through 2.33.7
- Coder versions 2.34.0 and 2.34.1
Discovery Timeline
- 2026-10-17 - CVE-2026-111932 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-111932
Vulnerability Analysis
Coder exposes deployment-wide appearance settings that let administrators customize the branding of the web interface. Two of these fields, ApplicationName and LogoURL, are written directly into HTML templates rendered by the dashboard and into the HTML bodies of SMTP notification emails.
Because the values are interpolated into HTML output without being escaped, attacker-controlled markup is parsed as live HTML by downstream clients. The injection is persistent: once the appearance settings are saved, every page load and every outbound notification email replays the payload until an administrator reverts the configuration.
The practical impact centers on social engineering. Attackers can rewrite the product name, swap the logo for an attacker-controlled image, add fake login prompts, or embed misleading links in notification emails that appear to originate from the legitimate Coder deployment.
Root Cause
The root cause is improper neutralization of input during web page generation [CWE-79]. The template renderer trusts the appearance-settings fields as safe HTML rather than treating them as untrusted text requiring context-appropriate escaping. Email templates reuse the same unescaped values when building HTML message bodies.
Attack Vector
Exploitation requires an authenticated account holding the Owner role, which limits the vulnerability to privileged insiders or attackers who have already compromised an Owner account. The attacker edits the deployment appearance configuration and stores HTML content in the ApplicationName or LogoURL fields. The payload then renders for every user who loads the dashboard or receives an SMTP notification from the deployment.
No verified public exploit code was identified at the time of publication. Technical details are published in the GitHub Security Advisory GHSA-h58c-xccx-75m3 and the Vulncheck advisory on stored HTML injection via appearance settings.
Detection Methods for CVE-2026-111932
Indicators of Compromise
- Appearance-setting values containing HTML tags, inline event handlers, or embedded URLs in the ApplicationName or LogoURL fields.
- Unexpected modifications to deployment appearance settings in Coder audit logs, especially from Owner accounts that do not normally manage branding.
- Outbound SMTP notification emails whose rendered subject or body contains unexpected branding, hyperlinks, or markup.
Detection Strategies
- Query the Coder database or administrative API for the current values of ApplicationName and LogoURL, and alert on values that contain <, >, javascript:, or non-image URL schemes.
- Review audit logs for UpdateAppearanceConfig or equivalent configuration-change events and correlate them with the acting user and source IP.
- Compare rendered dashboard HTML and outbound email HTML against a known-good branding baseline to detect injected markup.
Monitoring Recommendations
- Forward Coder audit logs to a centralized logging platform and alert on appearance-setting changes.
- Monitor Owner-role account activity for anomalous administrative actions, including off-hours configuration changes.
- Inspect outbound email gateways for notification messages whose HTML content deviates from the expected template.
How to Mitigate CVE-2026-111932
Immediate Actions Required
- Upgrade Coder to a patched release: 2.29.17, 2.32.7, 2.33.8, or 2.34.2 or later, depending on your current branch.
- Audit the current ApplicationName and LogoURL values and remove any HTML markup, inline scripts, or unexpected URLs.
- Review the list of accounts holding the Owner role and revoke the role from any account that does not require it.
Patch Information
Coder has released fixed versions 2.29.17, 2.32.7, 2.33.8, and 2.34.2. The patches apply context-appropriate escaping when rendering ApplicationName and LogoURL into dashboard HTML and SMTP notification templates. Patch details and version mapping are available in GitHub Security Advisory GHSA-h58c-xccx-75m3.
Workarounds
- Restrict the Owner role to a minimal set of trusted administrators and require multi-factor authentication on those accounts.
- Reset ApplicationName and LogoURL to plain-text and image-only values, and audit them on a recurring schedule until patching is complete.
- Temporarily disable SMTP notifications if branding fields cannot be sanitized, to prevent injected markup from reaching email recipients.
# Verify the installed Coder version before and after upgrade
coder version
# Example upgrade for a Linux host using the official install script
curl -L https://coder.com/install.sh | sh
# Inspect current appearance settings via the Coder API
curl -H "Coder-Session-Token: $CODER_SESSION_TOKEN" \
https://coder.example.com/api/v2/appearance
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

