<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 28 Sep 2026 18:32:31 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-76909</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-76909</link>
      <description>&lt;p&gt;Unleash is an open-source feature management platform. Prior to 8.0.3, the change-request approval email template at src/mailtemplates/requested-cr-approval/requested-cr-approval.html.mustache renders the user-controlled changeRequestTitle, requesterName, and requesterEmail values without HTML escaping, and sendRequestedCRApprovalEmail passes those values to Mustache rendering. A project member who can create a change request when approval emails are enabled can inject HTML into an approver&amp;#39;s notification, allowing forged links, tracking content, or visually altered email content. This issue is fixed in version 8.0.3.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Unleash is an open-source feature management platform. Prior to 8.0.3, the change-request approval email template at src/mailtemplates/requested-cr-approval/requested-cr-approval.html.mustache renders the user-controlled changeRequestTitle, requesterName, and requesterEmail values without HTML escaping, and sendRequestedCRApprovalEmail passes those values to Mustache rendering. A project member who can create a change request when approval emails are enabled can inject HTML into an approver&amp;#39;s notification, allowing forged links, tracking content, or visually altered email content. This issue is fixed in version 8.0.3.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-76909</guid>
    </item>
    <item>
      <title>GHSA-7hvx-28gp-mf6j — Unleash: CR-approval email renders user-controlled raw HTML</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-7hvx-28gp-mf6j</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: unleash-server&lt;/p&gt;
&lt;p&gt;### 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&amp;#39;t sanitize input.&lt;/p&gt;
&lt;p&gt;### Details
`src/mailtemplates/requested-cr-approval/requested-cr-approval.html.mustache` uses Mustache triple-stash syntax for fields that can originate from users:&lt;/p&gt;
&lt;p&gt;```mustache
{{{ changeRequestTitle }}}
{{{ requesterName }}}
{{{ requesterEmail }}}
{{{ changeRequestLink }}}
```&lt;/p&gt;
&lt;p&gt;Triple-stash disables HTML escaping even when Mustache&amp;#39;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`.&lt;/p&gt;
&lt;p&gt;### PoC
1. Use an Enterprise deployment with change requests and approval emails enabled.
2. As a project member who can create change requests, set a display name or change-request title to HTML such as:&lt;/p&gt;
&lt;p&gt;```html
&amp;lt;/a&amp;gt;&amp;lt;a href=&amp;#34;https://example.com&amp;#34;&amp;gt;Approve change request&amp;lt;/a&amp;gt;
```&lt;/p&gt;
&lt;p&gt;3. Create a change request that requires approval.
4. Observe that the approval email contains attacker-controlled raw HTML instead of escaped text.&lt;/p&gt;
&lt;p&gt;### Impact
Change-request approvers can receive forged links, tracking pixels, or visually altered email content.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: unleash-server&lt;/p&gt;
&lt;p&gt;### 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&amp;#39;t sanitize input.&lt;/p&gt;
&lt;p&gt;### Details
`src/mailtemplates/requested-cr-approval/requested-cr-approval.html.mustache` uses Mustache triple-stash syntax for fields that can originate from users:&lt;/p&gt;
&lt;p&gt;```mustache
{{{ changeRequestTitle }}}
{{{ requesterName }}}
{{{ requesterEmail }}}
{{{ changeRequestLink }}}
```&lt;/p&gt;
&lt;p&gt;Triple-stash disables HTML escaping even when Mustache&amp;#39;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`.&lt;/p&gt;
&lt;p&gt;### PoC
1. Use an Enterprise deployment with change requests and approval emails enabled.
2. As a project member who can create change requests, set a display name or change-request title to HTML such as:&lt;/p&gt;
&lt;p&gt;```html
&amp;lt;/a&amp;gt;&amp;lt;a href=&amp;#34;https://example.com&amp;#34;&amp;gt;Approve change request&amp;lt;/a&amp;gt;
```&lt;/p&gt;
&lt;p&gt;3. Create a change request that requires approval.
4. Observe that the approval email contains attacker-controlled raw HTML instead of escaped text.&lt;/p&gt;
&lt;p&gt;### Impact
Change-request approvers can receive forged links, tracking pixels, or visually altered email content.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-7hvx-28gp-mf6j</guid>
    </item>
  </channel>
</rss>
