What is the CVSS score of CVE-2026-58431?

CVE-2026-58431 has a CVSS 3.1 base score of 4.3 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N. EPSS exploitation probability: 0.1%.

Is there a patch available for CVE-2026-58431?

Yes, a patch is available for CVE-2026-58431. Update the affected software to the latest version immediately.

Gitea CVE-2026-58431

EUVD-2026-58158 MEDIUM

Incorrect Authorization (CWE-863)

2026-07-21 https://github.com/go-gitea/gitea

GHSA-h56g-4qw7-2mxg

Authentication Bypass Gitea

4.3

CVSS 3.1 · Vendor: https://github.com/go-gitea/gitea

Severity by source

Vendor (https://github.com/go-gitea/gitea) PRIMARY

4.3 MEDIUM

AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

vuln.today AI

4.3 MEDIUM

Network-accessible API requiring authenticated team membership (PR:L); metadata-only disclosure drives C:L with no integrity or availability impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

SUSE

MEDIUM

qualitative

Primary rating from Vendor (https://github.com/go-gitea/gitea).

CVSS VectorVendor: https://github.com/go-gitea/gitea

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Lifecycle Timeline

Source Code Evidence Fetched

Jul 22, 2026 - 02:54 vuln.today

Analysis Generated

Jul 22, 2026 - 02:54 vuln.today

DescriptionCVE.org

Summary

Gitea's /api/v1/teams/{id} API routes do not correctly enforce the public-only access token restriction.

A public-only token is intended to limit API access to public repositories and public organizations. However, several team API routes continue to return private team repository metadata and private team activity feed entries when called with a public-only token.

Details

The /api/v1/teams/{teamid} route group uses:

orgAssignment(false, true)

This loads ctx.Org.Team, but does not load ctx.Org.Organization.

The checkTokenPublicOnly middleware checks organization visibility through ctx.Org.Organization. When ctx.Org.Organization is nil, the organization visibility check silently passes.

In addition, the team repository handlers return repositories without applying repository-level public-only filtering:

repo_model.GetTeamRepositories(...)
convert.ToRepo(...)

They do not call:

ctx.TokenCanAccessRepo(repo)

The team activity feed handler also sets:

IncludePrivate: true

but does not apply:

opts.ApplyPublicOnly(ctx.PublicOnly)

PoC

Vulnerability is verified on latest gitea release (1.26.2) and nightly build. Frist, create a public-only organization-scoped token for a user who is a member of a team in a private org with private repositories:

Use the returned token to request team repositories:

Expected result: Private repositories should be hidden or rejected for a public-only token. Actual result: Private team repository metadata is returned.

The team activity feed endpoint can be tested similarly:

Impact

A public-only token can access private team resources that should be hidden from that token.

AnalysisAI

Incorrect authorization enforcement in Gitea's team API routes exposes private repository metadata and activity feed entries to public-only access tokens. Affected versions through 1.26.2 allow an authenticated team member holding a public-only scoped token to bypass the intended access restriction and retrieve private team repository listings and private activity feed data via /api/v1/teams/{id} endpoints. Publicly available exploit code (PoC) has been verified against Gitea 1.26.2 and nightly builds; no KEV listing at time of analysis. EPSS data not provided, but the CVSS score of 4.3 and limited confidentiality impact (metadata only, no code exfiltration) suggest moderate real-world risk.

Technical ContextAI

Gitea is a self-hosted Git service written in Go. The affected component is the team API route group at /api/v1/teams/{teamid}, which uses orgAssignment(false, true) - this loads ctx.Org.Team but intentionally does not load ctx.Org.Organization. The checkTokenPublicOnly middleware enforces the public-only token restriction by checking organization visibility through ctx.Org.Organization; when that value is nil (as it is for team routes), the visibility check silently passes - a classic nil-dereference bypass pattern. Additionally, team repository handlers invoke repo_model.GetTeamRepositories() and convert.ToRepo() without calling ctx.TokenCanAccessRepo(repo), bypassing per-repository public-only filtering. The team activity feed handler explicitly sets IncludePrivate: true without applying opts.ApplyPublicOnly(ctx.PublicOnly). The root cause class is CWE-863 (Incorrect Authorization) - the authorization logic is present but fails to execute due to missing context initialization on the team route group. Affected package: pkg:go/gitea.dev versions prior to 1.27.0.

RemediationAI

Upgrade to Gitea v1.27.0 or later, which resolves the authorization bypass by correctly loading ctx.Org.Organization in team API routes and applying ctx.TokenCanAccessRepo(repo) filtering and opts.ApplyPublicOnly(ctx.PublicOnly) to team repository and activity feed handlers respectively. The release is available at https://github.com/go-gitea/gitea/releases/tag/v1.27.0. If immediate upgrade is not possible, a compensating control is to revoke all public-only organization-scoped tokens and restrict API token creation until the patch is applied - this removes the precondition for exploitation but also disrupts legitimate public-only API integrations. Alternatively, network-level ACLs can restrict /api/v1/teams/* endpoints to trusted internal IP ranges, though this may impact legitimate external integrations. The GitHub Security Advisory is at https://github.com/go-gitea/gitea/security/advisories/GHSA-h56g-4qw7-2mxg.