No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Sat, 07 Nov 2026 07:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 06 Nov 2026 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
Sun, 01 Nov 2026 12:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Gitea
Gitea gitea |
|
| Vendors & Products |
Gitea
Gitea gitea |
Sun, 01 Nov 2026 10:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | `DELETE /api/v1/orgs/{org}/repos` deletes all repositories of an organization, but it did not enforce the public-only restriction of access tokens: the route only checked that the organization itself was public. A public-only token of an owner of a public organization could therefore permanently delete the organization's private repositories, which such a token must not reach. Routes that require organization ownership now reject public-only tokens. | |
| Title | Gitea public-only token bypass on bulk organization repository deletion | |
| Weaknesses | CWE-863 | |
| References |
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: Gitea
Published:
Updated: 2026-11-06T15:12:41.402Z
Reserved: 2026-11-01T08:48:41.157Z
Link: CVE-2026-119441
Updated: 2026-11-06T15:12:32.285Z
Status : Deferred
Published: 2026-11-01T10:18:36.643
Modified: 2026-11-06T16:17:51.940
Link: CVE-2026-119441
No data.
OpenCVE Enrichment
Updated: 2026-11-06T17:45:06Z