CVE-2026-76909: Unleash: CR-approval email renders user-controlled raw HTML
Summary The change-request approval HTML email template renders fields as raw HTML. User who can create a change request can inject HTML into approval notification emails. I was not able to confirm Enterprise platform is using vulnerable code nor that it doesn't sanitize input.
Published Sep 22, 2026
Affected packages
unleash-server
- Ecosystem
- npm
- Affected
- < 8.0.3
- Fixed in
- 8.0.3
- Check
npm ls unleash-server
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
The change-request approval HTML email template renders fields as raw HTML. User who can create a change request can inject HTML into approval notification emails. I was not able to confirm Enterprise platform is using vulnerable code nor that it doesn't sanitize input.
Details
src/mailtemplates/requested-cr-approval/requested-cr-approval.html.mustache uses Mustache triple-stash syntax for fields that can originate from users:
{{{ changeRequestTitle }}}
{{{ requesterName }}}
{{{ requesterEmail }}}
{{{ changeRequestLink }}}Triple-stash disables HTML escaping even when Mustache's global escape function is safe. The related renderer is sendRequestedCRApprovalEmail in src/lib/services/email-service.ts, which renders the template with Mustache.render.
PoC
- Use an Enterprise deployment with change requests and approval emails enabled.
- As a project member who can create change requests, set a display name or change-request title to HTML such as:
Approve change request- Create a change request that requires approval.
- Observe that the approval email contains attacker-controlled raw HTML instead of escaped text.
Impact
Change-request approvers can receive forged links, tracking pixels, or visually altered email content.
Credited to Tymek.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-76910
Unleash: Clone-feature lets a user copy a feature from a project they cannot read
medium5.3Sep 22, 2026CVE-2026-77425
Unleash: A project member can reorder activation strategies belonging to any other project / environment (cross-project integrity write), bypassing project RBAC and the audit log
medium4.3Sep 22, 2026CVE-2026-77426
Unleash: Missing await on permission check + cross-project IDOR in admin API
high7.1Sep 22, 2026CVE-2026-63004
Unleash: Addon webhook URL is dialed server-side with no internal-address filtering, enabling SSRF to internal services / cloud metadata and exfiltration of configured request headers
medium5.5Aug 21, 2026CVE-2026-63462
Unleash: Unauthenticated single-request DoS via OpenAPI validation error formatter
high7.5Aug 21, 2026CVE-2026-63466
Unleash: Global Mustache.escape override disables HTML escaping process-wide, enabling Slack/Teams link-injection via unrestricted username
medium4.1Aug 21, 2026
