<?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:21:11 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-76910</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-76910</link>
      <description>&lt;p&gt;Unleash is an open-source feature management platform. Prior to 8.0.3, cloneFeatureToggle and POST /api/admin/projects/:projectId/features/:featureName/clone authorize creation in the destination project but do not verify access to the source project. Because feature names are globally unique, a user with create or clone permission in one project who knows or guesses another project&amp;#39;s feature name can copy that feature into the authorized project and inspect its strategy parameters, constraints, variants, and variant payloads. 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, cloneFeatureToggle and POST /api/admin/projects/:projectId/features/:featureName/clone authorize creation in the destination project but do not verify access to the source project. Because feature names are globally unique, a user with create or clone permission in one project who knows or guesses another project&amp;#39;s feature name can copy that feature into the authorized project and inspect its strategy parameters, constraints, variants, and variant payloads. 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-76910</guid>
    </item>
    <item>
      <title>GHSA-8xcj-9hfr-fh9j — Unleash: Clone-feature lets a user copy a feature from a project they cannot read</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-8xcj-9hfr-fh9j</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: unleash-server&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The clone-feature endpoint supports copying features across projects, but it does not verify that the caller can access the source project. A user with _create_ permissions in one project can clone a feature from another project they cannot read and then inspect the copied configuration.&lt;/p&gt;
&lt;p&gt;This vulnerability cannot be confirmed without Enterprise access. Report is based on a circumstantial evidence in the open-source repository.&lt;/p&gt;
&lt;p&gt;### Details
`src/lib/features/feature-toggle/feature-toggle-service.ts` implements `cloneFeatureToggle`. This operation needs authorization for both sides: permission to read/copy the source feature and permission to create the destination feature.&lt;/p&gt;
&lt;p&gt;The clone path validates permissions against the destination project, but not against the source project that owns `featureName`. Because feature names are globally unique, a caller can reference a feature outside projects they can access.&lt;/p&gt;
&lt;p&gt;### PoC
1. Create or identify two projects: `P1` with a private or restricted feature named `secret-feature`, and `P2` where the attacker has clone/create permissions.
2. Authenticate as the attacker.
3. Send:&lt;/p&gt;
&lt;p&gt;```http
POST /api/admin/projects/P2/features/secret-feature/clone
Content-Type: application/json&lt;/p&gt;
&lt;p&gt;{ &amp;#34;name&amp;#34;: &amp;#34;secret-feature-copy&amp;#34; }
```&lt;/p&gt;
&lt;p&gt;4. Open `P2` and inspect `secret-feature-copy`. Verify if strategy parameters, constraints, variants, and variant payloads from the source feature have been copied.&lt;/p&gt;
&lt;p&gt;### Impact
Users with permissions on one project…&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&lt;/p&gt;
&lt;p&gt;The clone-feature endpoint supports copying features across projects, but it does not verify that the caller can access the source project. A user with _create_ permissions in one project can clone a feature from another project they cannot read and then inspect the copied configuration.&lt;/p&gt;
&lt;p&gt;This vulnerability cannot be confirmed without Enterprise access. Report is based on a circumstantial evidence in the open-source repository.&lt;/p&gt;
&lt;p&gt;### Details
`src/lib/features/feature-toggle/feature-toggle-service.ts` implements `cloneFeatureToggle`. This operation needs authorization for both sides: permission to read/copy the source feature and permission to create the destination feature.&lt;/p&gt;
&lt;p&gt;The clone path validates permissions against the destination project, but not against the source project that owns `featureName`. Because feature names are globally unique, a caller can reference a feature outside projects they can access.&lt;/p&gt;
&lt;p&gt;### PoC
1. Create or identify two projects: `P1` with a private or restricted feature named `secret-feature`, and `P2` where the attacker has clone/create permissions.
2. Authenticate as the attacker.
3. Send:&lt;/p&gt;
&lt;p&gt;```http
POST /api/admin/projects/P2/features/secret-feature/clone
Content-Type: application/json&lt;/p&gt;
&lt;p&gt;{ &amp;#34;name&amp;#34;: &amp;#34;secret-feature-copy&amp;#34; }
```&lt;/p&gt;
&lt;p&gt;4. Open `P2` and inspect `secret-feature-copy`. Verify if strategy parameters, constraints, variants, and variant payloads from the source feature have been copied.&lt;/p&gt;
&lt;p&gt;### Impact
Users with permissions on one project…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-8xcj-9hfr-fh9j</guid>
    </item>
  </channel>
</rss>
