Gitea: Notification API leaks private issue metadata after access revocation (CVE-2026-58419)
Gitea Notification API in versions prior to 1.26.4 leaks private issue and pull request metadata through the 'subject' field of notification threads after a user's access to a private repository has been revoked. While the 'repository' field is correctly nulled, the 'subject' field still exposes sensitive information such as issue titles, URLs, state, and comment activity. This allows users who lost access to continue observing ongoing activity on private issues or pull requests via notifications.
AI Analysis
Technical Summary
An information disclosure vulnerability exists in Gitea's Notification API where users who have had their access to a private repository revoked can still access private metadata through the 'subject' field in notification threads. Although the 'repository' field is set to null after access revocation, the 'subject' field remains accessible and contains private issue or pull request titles, URLs, state, and comment activity metadata. This issue was confirmed in Gitea v1.26.2 and affects all versions prior to 1.26.4. The vulnerability allows continued visibility into private repository activity through notifications despite access revocation.
Potential Impact
Users who no longer have access to a private repository can still obtain private issue or pull request information including titles, URLs, states, and comment activity via the notification API. This results in unauthorized disclosure of sensitive repository metadata and ongoing activity, violating access control expectations.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The affected versions are prior to 1.26.4; upgrading to version 1.26.4 or later is expected to address this issue. Until patched, restrict notification API access or revoke notification subscriptions when repository access is revoked to reduce exposure.
Gitea: Notification API leaks private issue metadata after access revocation (CVE-2026-58419)
Description
Gitea Notification API in versions prior to 1.26.4 leaks private issue and pull request metadata through the 'subject' field of notification threads after a user's access to a private repository has been revoked. While the 'repository' field is correctly nulled, the 'subject' field still exposes sensitive information such as issue titles, URLs, state, and comment activity. This allows users who lost access to continue observing ongoing activity on private issues or pull requests via notifications.
CVSS v3.1
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
An information disclosure vulnerability exists in Gitea's Notification API where users who have had their access to a private repository revoked can still access private metadata through the 'subject' field in notification threads. Although the 'repository' field is set to null after access revocation, the 'subject' field remains accessible and contains private issue or pull request titles, URLs, state, and comment activity metadata. This issue was confirmed in Gitea v1.26.2 and affects all versions prior to 1.26.4. The vulnerability allows continued visibility into private repository activity through notifications despite access revocation.
Potential Impact
Users who no longer have access to a private repository can still obtain private issue or pull request information including titles, URLs, states, and comment activity via the notification API. This results in unauthorized disclosure of sensitive repository metadata and ongoing activity, violating access control expectations.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The affected versions are prior to 1.26.4; upgrading to version 1.26.4 or later is expected to address this issue. Until patched, restrict notification API access or revoke notification subscriptions when repository access is revoked to reduce exposure.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Gitea
- Date Reserved
- 2026-06-30T18:57:20.613Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
- Gcve Source
- db.gcve.eu
Threat ID: 6a483c9d27e9c79719d7f5e6
Added to database: 07/03/2026, 22:50:05 UTC
Last enriched: 07/22/2026, 01:08:30 UTC
Last updated: 07/22/2026, 01:08:30 UTC
Views: 66
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.