<?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>Wed, 30 Sep 2026 06:59:28 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-58417</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-58417</link>
      <description>&lt;p&gt;REST API exposes organization membership of private organizations to public&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;REST API exposes organization membership of private organizations to public&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-58417</guid>
    </item>
    <item>
      <title>GHSA-jr5x-6h83-wrxf — Gitea: REST API exposes organization membership of private organizations to public</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-jr5x-6h83-wrxf</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: gitea.dev&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The endpoint  &amp;#34;/orgs/{org}/public_members/{username}&amp;#34; + GET exposes organization membership of public members in a private organization.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;1. Spin up the nightly container of Gitea.
2. Perform the default installation.
3. Register a new user (let&amp;#39;s call this user &amp;#34;user1&amp;#34;).
4. Create a new organization with &amp;#34;private&amp;#34; visibility. We will refer to this organization as &amp;#34;user1org&amp;#34;.
5. Make the user &amp;#34;user1&amp;#34; inside the organization visible.
6. Log out and register a new user (&amp;#34;user2&amp;#34;).
7. Create an access token for &amp;#34;user2&amp;#34; with full access to the API.
8. Use the endpoint &amp;#34;/orgs/{org}/public_members/{username}&amp;#34; + GET with the correct username of &amp;#34;user1&amp;#34;, organization name, and access token of &amp;#34;user2&amp;#34; to query whether &amp;#34;user1&amp;#34; is a member of the organization. The following curl command demonstrates the usage:&lt;/p&gt;
&lt;p&gt;curl -X &amp;#39;GET&amp;#39; \
  &amp;#39;http://localhost:4700/api/v1/orgs/user1org/public_members/user1&amp;#39; \
  -H &amp;#39;accept: application/json&amp;#39; \
  -H &amp;#39;authorization: token &amp;lt;user2-token&amp;gt;&amp;#39;&lt;/p&gt;
&lt;p&gt;9. You will receive status code 204, which leaks the organization membership.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;The vulnerability discloses organization membership. An information that is not accessible via the web app (the organization is hidden, and therefore, the organization membership on the user&amp;#39;s profile page is also hidden).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: gitea.dev&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The endpoint  &amp;#34;/orgs/{org}/public_members/{username}&amp;#34; + GET exposes organization membership of public members in a private organization.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;1. Spin up the nightly container of Gitea.
2. Perform the default installation.
3. Register a new user (let&amp;#39;s call this user &amp;#34;user1&amp;#34;).
4. Create a new organization with &amp;#34;private&amp;#34; visibility. We will refer to this organization as &amp;#34;user1org&amp;#34;.
5. Make the user &amp;#34;user1&amp;#34; inside the organization visible.
6. Log out and register a new user (&amp;#34;user2&amp;#34;).
7. Create an access token for &amp;#34;user2&amp;#34; with full access to the API.
8. Use the endpoint &amp;#34;/orgs/{org}/public_members/{username}&amp;#34; + GET with the correct username of &amp;#34;user1&amp;#34;, organization name, and access token of &amp;#34;user2&amp;#34; to query whether &amp;#34;user1&amp;#34; is a member of the organization. The following curl command demonstrates the usage:&lt;/p&gt;
&lt;p&gt;curl -X &amp;#39;GET&amp;#39; \
  &amp;#39;http://localhost:4700/api/v1/orgs/user1org/public_members/user1&amp;#39; \
  -H &amp;#39;accept: application/json&amp;#39; \
  -H &amp;#39;authorization: token &amp;lt;user2-token&amp;gt;&amp;#39;&lt;/p&gt;
&lt;p&gt;9. You will receive status code 204, which leaks the organization membership.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;The vulnerability discloses organization membership. An information that is not accessible via the web app (the organization is hidden, and therefore, the organization membership on the user&amp;#39;s profile page is also hidden).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-jr5x-6h83-wrxf</guid>
    </item>
  </channel>
</rss>
