Notification API Leaks Private Repository Issue Titles After Collaborator Permission Revocation
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Gitea | Gitea Open Source Git Server | unaffected |
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| Gitea | Gitea | — |
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-2vgv-hgv4-22mh | Gitea improperly exposes issue and pull request titles |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.406% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:gitea:gitea:*:*:*:*:*:-:*:* |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Gitea
Gitea gitea |
|
| Vendors & Products |
Gitea
Gitea gitea |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Gitea's notification API does not re-validate repository access permissions when returning notification details. After a user's access to a private repository is revoked, they may still view issue and pull request titles through previously received notifications. | |
| Title | Notification API Leaks Private Repository Issue Titles After Collaborator Permission Revocation | |
| Weaknesses | CWE-200 | |
| References |
|