CVE-2026-111932 coder CVE debrief

Who should care

Defenders responsible for Coder deployments, especially those with untrusted users or where users have the Owner role, should assess their exposure to this vulnerability. They should verify their Coder versions, restrict Owner role assignments, and monitor for suspicious activity.

Why it matters

CVE-2026-111932 is a stored HTML injection vulnerability in Coder that allows attackers with the Owner role to store malicious HTML markup. Defenders should verify exposure, restrict Owner role assignments, and monitor for suspicious activity. The vulnerability has a CVSS score of 4.8 and is considered medium severity.

• Potential for phishing attacks through stored HTML injection in Coder dashboard and SMTP notification emails
• Possible impact on user trust due to rendering of untrusted HTML content
• Need for verification of Coder versions and configurations to identify exposure
• Requirement for monitoring Coder activity for suspicious behavior

Technical summary

The Coder application, versions before 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, contains a stored HTML injection vulnerability. This vulnerability allows users with the Owner role to store HTML markup in the ApplicationName and LogoURL appearance settings. The stored HTML can render in the Coder dashboard and in SMTP notification emails sent to other deployment users.

Defensive priority

Defenders should prioritize verifying exposure in their Coder deployments, especially those with untrusted users or where users have the Owner role. They should also monitor for suspicious activity and update to a fixed version as soon as possible.

Recommended defensive actions

• Verify Coder deployment versions and configurations to identify potential exposure.
• Restrict Owner role assignments to trusted users.
• Monitor Coder dashboard and SMTP notification emails for suspicious activity.
• Update Coder to a fixed version (2.29.17, 2.32.7, 2.33.8, or 2.34.2) as soon as possible.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record and NVD entry provide information about the vulnerability, but details about exploitation or impact are limited. The vendor and product information is not fully populated, indicating a need for further verification.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.