https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 08:25:01 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-333526 EUVD-2026-333526 https://cve.radiocsirt.org/vuln/euvd-2026-333526 https://cve.radiocsirt.org/vuln/fkie_cve-2026-22555 <p>Gitea versions before 1.26.0 allow API users to fork a repository into an organization without first passing the CanCreateOrgRepo check, which can expose organization secrets.</p> <p>Gitea versions before 1.26.0 allow API users to fork a repository into an organization without first passing the CanCreateOrgRepo check, which can expose organization secrets.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-22555 https://cve.radiocsirt.org/vuln/ghsa-fhx7-m96w-mv29 <p><strong>Affected:</strong> Go: code.gitea.io/gitea</p> <p>## Summary</p> <p>The API endpoint `POST /api/v1/repos/{owner}/{repo}/forks` only checks `IsOrgMember()` when a user forks a repository into an organization, but does not check `CanCreateOrgRepo()`. The web UI fork handler correctly checks both. This allows a read-only organization member — in a team with `can_create_org_repo=false` — to create repositories in the organization namespace via the API. The attacker receives full admin permissions on the forked repository, can enable Actions, push arbitrary workflow files, and exfiltrate all organization-level CI/CD secrets (deploy keys, cloud credentials, API tokens) through the runner infrastructure.</p> <p>## Steps To Reproduce</p> <p>### 1. Environment setup</p> <p>Start a Gitea instance with Actions enabled:</p> <p>```bash # docker-compose.yml cat &gt; docker-compose.yml &lt;&lt; &#39;EOF&#39; version: &#39;3&#39; services: gitea: image: gitea/gitea:1.23 container_name: gitea-poc ports: - &#34;3000:3000&#34; volumes: - gitea-data:/data environment: - GITEA__database__DB_TYPE=sqlite3 - GITEA__server__ROOT_URL=http://localhost:3000/ - GITEA__security__INSTALL_LOCK=true - GITEA__actions__ENABLED=true volumes: gitea-data: EOF</p> <p>docker compose up -d # Wait for startup sleep 15</p> <p># Create admin user docker exec -u git gitea-poc gitea admin user create \ --admin --username admin --password &#39;Admin1234!&#39; \ --email admin@example.com --must-change-password=false ```</p> <p>### 2. Create the target environment (as admin)</p> <p>```bash # Get admin…</p> <p><strong>Affected:</strong> Go: code.gitea.io/gitea</p> <p>## Summary</p> <p>The API endpoint `POST /api/v1/repos/{owner}/{repo}/forks` only checks `IsOrgMember()` when a user forks a repository into an organization, but does not check `CanCreateOrgRepo()`. The web UI fork handler correctly checks both. This allows a read-only organization member — in a team with `can_create_org_repo=false` — to create repositories in the organization namespace via the API. The attacker receives full admin permissions on the forked repository, can enable Actions, push arbitrary workflow files, and exfiltrate all organization-level CI/CD secrets (deploy keys, cloud credentials, API tokens) through the runner infrastructure.</p> <p>## Steps To Reproduce</p> <p>### 1. Environment setup</p> <p>Start a Gitea instance with Actions enabled:</p> <p>```bash # docker-compose.yml cat &gt; docker-compose.yml &lt;&lt; &#39;EOF&#39; version: &#39;3&#39; services: gitea: image: gitea/gitea:1.23 container_name: gitea-poc ports: - &#34;3000:3000&#34; volumes: - gitea-data:/data environment: - GITEA__database__DB_TYPE=sqlite3 - GITEA__server__ROOT_URL=http://localhost:3000/ - GITEA__security__INSTALL_LOCK=true - GITEA__actions__ENABLED=true volumes: gitea-data: EOF</p> <p>docker compose up -d # Wait for startup sleep 15</p> <p># Create admin user docker exec -u git gitea-poc gitea admin user create \ --admin --username admin --password &#39;Admin1234!&#39; \ --email admin@example.com --must-change-password=false ```</p> <p>### 2. Create the target environment (as admin)</p> <p>```bash # Get admin…</p> https://cve.radiocsirt.org/vuln/ghsa-fhx7-m96w-mv29 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1172 <p>Ein Angreifer kann mehrere Schwachstellen in Gitea ausnutzen, um Informationen offenzulegen, um Sicherheitsvorkehrungen zu umgehen, und um einen Cross-Site Scripting Angriff durchzuführen.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Gitea ausnutzen, um Informationen offenzulegen, um Sicherheitsvorkehrungen zu umgehen, und um einen Cross-Site Scripting Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1172