https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 20:09:21 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-333343 EUVD-2026-333343 https://cve.radiocsirt.org/vuln/euvd-2026-333343 https://cve.radiocsirt.org/vuln/fkie_cve-2026-58419 <p>Notification API leaks private issue metadata after access revocation</p> <p>Notification API leaks private issue metadata after access revocation</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-58419 https://cve.radiocsirt.org/vuln/ghsa-44qc-pgvp-wx7v <p><strong>Affected:</strong> Go: code.gitea.io/gitea</p> <p># Summary</p> <p>An information disclosure issue in the Gitea Notification API allows users who have lost access to a private repository to continue accessing private issue or pull request information through existing notification threads. Although repository information is hidden after access revocation, the `subject` field remains accessible and continues to expose private metadata.</p> <p># Details</p> <p>CVE-2026-20800 was fixed in v1.25.4 to prevent users from accessing private repository information through notification APIs after their repository access had been revoked.</p> <p>During testing on Gitea v1.26.2, the `repository` field in `NotificationThread` responses is correctly set to `null` after access revocation. However, the associated `subject` field remains available.</p> <p>The exposed `subject` object may contain:</p> <p>* Private issue or pull request titles * Repository-related API and HTML URLs * Issue or pull request state * Latest comment URLs and comment identifiers</p> <p>Additionally, the exposed notification data is not limited to historical information. If new comments are added to the issue or pull request while the notification remains unread, fields such as `latest_comment_url` and `updated_at` continue to change. As a result, a user whose repository access has been revoked can still observe ongoing issue or pull request activity through notification APIs.</p> <p>The observed behavior suggests that access control is applied to the `repository` field but not consistently applied to the associat…</p> <p><strong>Affected:</strong> Go: code.gitea.io/gitea</p> <p># Summary</p> <p>An information disclosure issue in the Gitea Notification API allows users who have lost access to a private repository to continue accessing private issue or pull request information through existing notification threads. Although repository information is hidden after access revocation, the `subject` field remains accessible and continues to expose private metadata.</p> <p># Details</p> <p>CVE-2026-20800 was fixed in v1.25.4 to prevent users from accessing private repository information through notification APIs after their repository access had been revoked.</p> <p>During testing on Gitea v1.26.2, the `repository` field in `NotificationThread` responses is correctly set to `null` after access revocation. However, the associated `subject` field remains available.</p> <p>The exposed `subject` object may contain:</p> <p>* Private issue or pull request titles * Repository-related API and HTML URLs * Issue or pull request state * Latest comment URLs and comment identifiers</p> <p>Additionally, the exposed notification data is not limited to historical information. If new comments are added to the issue or pull request while the notification remains unread, fields such as `latest_comment_url` and `updated_at` continue to change. As a result, a user whose repository access has been revoked can still observe ongoing issue or pull request activity through notification APIs.</p> <p>The observed behavior suggests that access control is applied to the `repository` field but not consistently applied to the associat…</p> https://cve.radiocsirt.org/vuln/ghsa-44qc-pgvp-wx7v https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2149 <p>Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Gitea ausnutzen, um seine Privilegien zu erhöhen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren, vertrauliche Informationen offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.</p> <p>Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Gitea ausnutzen, um seine Privilegien zu erhöhen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren, vertrauliche Informationen offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2149