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.

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

MEDIUM

Incorrect Authorization (CWE-863)

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

GHSA-h56g-4qw7-2mxg

Gitea Authentication Bypass

4.3

CVSS 3.1 · GitHub Advisory

Severity by source

GitHub Advisory 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

Primary rating from GitHub Advisory.

CVSS VectorGitHub Advisory

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

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

DescriptionGitHub Advisory

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. …

Unlock full vulnerability intelligence

Risk assessment & exploitation conditions
Attack chain visualization
Remediation with exact patch versions
Threat intelligence from 22 sources
Personal watchlist & email alerts

Continue with Google Continue with GitHub

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access

Authenticate to Gitea as team member

Delivery

Create or obtain public-only org-scoped token

Exploit

Send GET request to /api/v1/teams/{id}/repos

Execution

Bypass public-only middleware due to nil org context

Impact

Receive private repository metadata in API response

Access

Authenticate to Gitea as team member

Delivery

Create or obtain public-only org-scoped token

Exploit

Send GET request to /api/v1/teams/{id}/repos

Execution

Bypass public-only middleware due to nil org context

Impact

Receive private repository metadata in API response

Vulnerability AssessmentAI

Exploitation	Exploitation requires three concurrent conditions: (1) the attacker must be an authenticated Gitea user who is a member of at least one team within a private organization, (2) that user must possess a public-only organization-scoped API token (a deliberate security-scoping feature available in Gitea's token management UI), and (3) the targeted organization must contain private repositories or private activity entries. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment	The CVSS 3.1 vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N scores 4.3 (Medium), which accurately reflects the bounded scope of impact: only metadata (repository names, activity feed entries) is disclosed, not repository content or credentials. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario	A developer or CI/CD service account holds a public-only organization-scoped Gitea API token intended to limit access to public resources. By sending authenticated GET requests to /api/v1/teams/{teamid}/repos or the team activity feed endpoint with this token, the attacker retrieves private repository names and organizational activity entries that should be hidden. …
Remediation	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. … Detailed patch versions, workarounds, and compensating controls in full report.