CVE-2026-58419: Gitea: Notification API leaks private issue metadata after access revocation
Summary 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.
Published Jul 21, 2026
Affected packages
code.gitea.io/gitea
- Ecosystem
- Go
- Affected
- < 1.26.3
- Fixed in
- 1.26.4
- Check
go list -m code.gitea.io/gitea
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
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.
Details
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.
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.
The exposed subject object may contain:
- Private issue or pull request titles
- Repository-related API and HTML URLs
- Issue or pull request state
- Latest comment URLs and comment identifiers
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.
The observed behavior suggests that access control is applied to the repository field but not consistently applied to the associated subject information.
PoC
Environment
- Gitea v1.26.2
- Private repository
Steps to Reproduce
- User
suncreates a private repository and grants read access to userli.
- User
lisubscribes to repository notifications.
- User
suncreates a private issue and adds a comment.
- User
lireceives a notification (thread_id = 14).
- User
sunrevokesli's repository access.
- User
lirequests:
GET /api/v1/repos/sun/{repo}/issues/1Response:
404 Not Found- User
lirequests:
GET /api/v1/notifications?all=true- User
lirequests:
GET /api/v1/notifications/threads/14Observed Result
The notification is returned successfully. The repository field is null, but the subject field still contains private issue metadata.
Example:
{
"id": 14,
"repository": null,
"subject": {
"title": "private issue title",
"url": "http://localhost:3000/api/v1/repos/sun/private-repo/issues/1",
"latest_comment_url": "http://localhost:3000/api/v1/repos/sun/private-repo/issues/comments/24",
"html_url": "http://localhost:3000/sun/private-repo/issues/1",
"state": "open"
}
}Expected Result
Users who no longer have access to a repository should not receive private issue or pull request information through notification APIs. The subject field should be removed, redacted, or otherwise protected by the same access controls applied to the repository field.
Detailed PoC
https://anonymous.4open.science/r/Gitea_PoC-EC93/1_poc_notification_leak
Impact
Affected Endpoints
GET /api/v1/notificationsGET /api/v1/notifications/threads/{id}
Prerequisites
- The user previously had legitimate access to the private repository.
- The notification was received before repository access was revoked.
Impact
- Disclosure of private issue or pull request titles.
- Disclosure of repository information through notification URLs.
- Disclosure of issue or pull request state.
- Disclosure of comment activity metadata.
- Continued visibility into issue or pull request activity after repository access has been revoked.
Tested Version
- Confirmed on v1.26.2.
Credited to ybsun0215.
References
- https://github.com/go-gitea/gitea/security/advisories/GHSA-44qc-pgvp-wx7v
- https://nvd.nist.gov/vuln/detail/CVE-2026-58419
- https://github.com/go-gitea/gitea/pull/38108
- https://github.com/go-gitea/gitea/commit/9e84deb969aff5c1115c2984e41250f28c78451f
- https://blog.gitea.com/release-of-1.26.3-and-1.26.4
- https://github.com/go-gitea/gitea/releases/tag/v1.26.4
- https://github.com/advisories/GHSA-44qc-pgvp-wx7v
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-20779
Gitea: TOTP TOCTOU race on web 2FA paths + missing replay check on Basic-Auth `X-Gitea-OTP` surface
high7.1Jul 21, 2026CVE-2026-20896
Gitea Docker image: `REVERSE_PROXY_TRUSTED_PROXIES = *` default lets any source IP impersonate any user via `X-WEBAUTH-USER`
critical9.8Jul 21, 2026CVE-2026-22874
Gitea: Incomplete SSRF Protection in Webhook and Migration Allow-list Default Filter
critical9.6Jul 21, 2026CVE-2026-23603
Gitea: Blind SSRF in OAuth2 avatar synchronization via unvalidated OIDC picture claim
low3.1Jul 21, 2026CVE-2026-24451
Gitea: Fork Synchronization Continues After Parent Repository Changes from Public to Private
high7.5Jul 21, 2026CVE-2026-25038
Gitea: Unauthorized Access to Labels of Private Organizations
high7.5Jul 21, 2026
