Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Cross-repository label-ID enumeration oracle via unscoped DeleteIssueLabel API

cve-program · severity unknownEUVD CVSS 3.1 2.7 CVSS 3.1 · 134c704f-9b21-4f2e-91b3-4a467353bcc0 · Secondary 2.7 LOWCVSS_V3 Publisher rating LOWFixed by code.gitea.io/gitea 1.27.0osv · severity unknownFixed by gitea.dev 1.27.0KEV status unknown

cve-program · CVE-2026-58445

Published

Cross-repository label-ID enumeration oracle via unscoped DeleteIssueLabel API

Read the publisher's advisory

euvd · EUVD-2026-58172

Published

Cross-repository label-ID enumeration oracle via unscoped DeleteIssueLabel API

Read the publisher's advisory

nvd · CVE-2026-58445

Published

Cross-repository label-ID enumeration oracle via unscoped DeleteIssueLabel API

Read the publisher's advisory

osv · GHSA-pgqf-926r-548m

Published

## Summary The API endpoint `DELETE /repos/{owner}/{repo}/issues/{index}/labels/{id}` loads the label by ID with a **global, unscoped** lookup and never verifies the label belongs to the URL's repository (or its owning organization). Because the response status differs by whether the label ID exists **anywhere on the instance** (204) versus not (422), an authenticated user can use the endpoint as a **cross-repository label-ID existence / enumeration oracle**, including for labels in repositories and organizations they cannot access. ## Severity - The leaked information is minimal (existence/count of label IDs instance-wide); **no label name, color, or owning repository is disclosed, and no cross-repository write occurs.** ## Affected / patched versions - **Affected:** through **1.26.3** (latest at time of report). - **Patched:** none yet. ## Details `DeleteIssueLabel` resolves the label with a global loader and never checks its scope: ```go // routers/api/v1/repo/issue_label.go (DeleteIssueLabel) label, err := issues_model.GetLabelByID(ctx, ctx.PathParamInt64("id")) // global, unscoped ``` `GetLabelByID` (`models/issues/label.go`) is `e.ID(labelID).Get(l)` with **no** `repo_id` / `org_id` filter. The handler never verifies `label.RepoID == ctx.Repo.Repository.ID` (nor the org-label equivalent), and the downstream `issue_service.RemoveLabel` (`services/issue/label.go`) only re-checks the doer's write permission on the **issue's own** repository — never that the label belongs to it. Every sibling label handler is correctly scoped — `GetLabel` / `EditLabel` / `DeleteLabel` (repo and org) use `GetLabelInRepoByID` / `GetLabelInOrgByID` and return 404 for a foreign ID. `DeleteIssueLabel` is the only outlier. **Why it is only an oracle:** `deleteIssueLabel` (`models/issues/issue_label.go`) deletes the `issue_label` row keyed by `(issue.ID, label.ID)`. For a foreign label, no such row exists → the function returns early **before** any mutation or comment creation. So there is no cross-repo write and no leak of the label's name. But the HTTP status differs: - label ID exists anywhere on the instance (incl. private repos/orgs) → **204 No Content** - label ID does not exist → **422** (`ErrLabelNotExist`) Label IDs are sequential auto-increment, so this enumerates the instance-wide label population and probes existence of specific IDs across tenant boundaries. ## Proof of Concept Verified end-to-end on a build of the `v1.26.3` tag. - `alice` (private repo `alice/secret`) creates a label → internal id **1**. - Attacker `bob` (separate user; public repo `bob/pub` with issue #1; **no access** to `alice/secret`) holds a token with `write:issue` on his own repo. ```text bob DELETE /api/v1/repos/bob/pub/issues/1/labels/1 -> HTTP 204 (alice's PRIVATE label id exists) bob DELETE /api/v1/repos/bob/pub/issues/1/labels/99999999 -> HTTP 422 (no such label) ``` Differing only by the label ID: `204` vs `422` distinguishes "label ID exists" from "does not exist." `bob` has zero rights to `alice/secret` but can still learn label id 1 exists. (Alice's label is untouched — no write.) Reproduction steps: 1. Create two users `alice`, `bob`. As `alice`, create a private repo and a label on it (note the label `id` from the API response). 2. As `bob`, create any repo with an issue, and a token with `write:issue`. 3. `curl -u bob:$T -X DELETE https://<gitea>/api/v1/repos/bob/pub/issues/1/labels/<alice_label_id>` → **204**. 4. `curl -u bob:$T -X DELETE https://<gitea>/api/v1/repos/bob/pub/issues/1/labels/99999999` → **422**. 5. The differing status across an ID `bob` cannot otherwise see is the oracle. ## Impact Cross-tenant authorization-key bypass producing a label-ID existence/enumeration oracle: an authenticated user can determine whether arbitrary label IDs (including in private repositories and organizations they cannot access) exist, and enumerate the instance-wide label population. ## Remediation Scope the loader like every sibling handler, returning 404 for a label that is not in the URL repository (or its owning organization), so the status no longer distinguishes existence: ```go // routers/api/v1/repo/issue_label.go — in DeleteIssueLabel, after loading the label if label.RepoID != ctx.Repo.Repository.ID && label.OrgID != ctx.Repo.Repository.OwnerID { ctx.APIErrorNotFound() return } ``` (Equivalently, resolve via `GetLabelInRepoByID` and, for org repositories, also accept the repo owner's org labels — mirroring the scoping in `GetLabel`/`EditLabel`/`DeleteLabel`.)

Read the publisher's advisory

osv · GO-2026-6067

Published

Gitea: Cross-repository label-ID enumeration oracle via unscoped DeleteIssueLabel API in gitea.dev

Read the publisher's advisory

Affected versions, risk and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

Risk history

Compare earlier KEV listings and EPSS scores. Advisory wording and affected versions have a separate history.

When does an EPSS score appear as a change?

A prediction change is reported when EPSS rises from below 10% to 10% or higher. Every daily score change from the last 30 days stays in this history. Before that, it keeps KEV changes and moves between EPSS bands (0.1%, 1%, 5%, 10%, 20%, 50% and 90%).

Advisory history

16 saved versions

See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.

How advisory history works

Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.

19 Nov 2026 17:49:37 UTC

Cross-repository label-ID enumeration oracle via unscoped DeleteIssueLabel API

euvd · EUVD-2026-58172 · Published

17 Nov 2026 17:35:31 UTC

Cross-repository label-ID enumeration oracle via unscoped DeleteIssueLabel API

euvd · EUVD-2026-58172 · Published

15 Nov 2026 16:47:10 UTC

Cross-repository label-ID enumeration oracle via unscoped DeleteIssueLabel API

euvd · EUVD-2026-58172 · Published

13 Nov 2026 16:01:40 UTC

Cross-repository label-ID enumeration oracle via unscoped DeleteIssueLabel API

euvd · EUVD-2026-58172 · Published

11 Nov 2026 15:00:38 UTC

Cross-repository label-ID enumeration oracle via unscoped DeleteIssueLabel API

euvd · EUVD-2026-58172 · Published

9 Nov 2026 14:06:57 UTC

Cross-repository label-ID enumeration oracle via unscoped DeleteIssueLabel API

euvd · EUVD-2026-58172 · Published

7 Nov 2026 13:24:20 UTC

Cross-repository label-ID enumeration oracle via unscoped DeleteIssueLabel API

euvd · EUVD-2026-58172 · Published

5 Nov 2026 12:41:23 UTC

Cross-repository label-ID enumeration oracle via unscoped DeleteIssueLabel API

euvd · EUVD-2026-58172 · Published

3 Nov 2026 12:00:11 UTC

Cross-repository label-ID enumeration oracle via unscoped DeleteIssueLabel API

euvd · EUVD-2026-58172 · Published

1 Nov 2026 11:23:17 UTC

Cross-repository label-ID enumeration oracle via unscoped DeleteIssueLabel API

euvd · EUVD-2026-58172 · Published

30 Oct 2026 10:50:27 UTC

Cross-repository label-ID enumeration oracle via unscoped DeleteIssueLabel API

euvd · EUVD-2026-58172 · Published

28 Oct 2026 08:36:41 UTC

Cross-repository label-ID enumeration oracle via unscoped DeleteIssueLabel API

euvd · EUVD-2026-58172 · Published

25 Oct 2026 14:19:16 UTC

Cross-repository label-ID enumeration oracle via unscoped DeleteIssueLabel API

nvd · CVE-2026-58445 · Published

24 Oct 2026 13:19:41 UTC

Gitea: Cross-repository label-ID enumeration oracle via unscoped DeleteIssueLabel API

osv · GHSA-pgqf-926r-548m · Published

24 Oct 2026 13:19:41 UTC

Gitea: Cross-repository label-ID enumeration oracle via unscoped DeleteIssueLabel API in gitea.dev

osv · GO-2026-6067 · Published

23 Oct 2026 15:48:27 UTC

Cross-repository label-ID enumeration oracle via unscoped DeleteIssueLabel API

cve-program · CVE-2026-58445 · Published

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 20 Nov 22:12 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current