How severe is GHSA-8629-vc8r-5p58?

GHSA-8629-vc8r-5p58 has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-8629-vc8r-5p58?

GHSA-8629-vc8r-5p58 affects the following packages: code.gitea.io/gitea (Go). Ecosystems affected: Go.

How do I fix GHSA-8629-vc8r-5p58?

Update code.gitea.io/gitea to 1.26.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8629-vc8r-5p58 is resolved across your whole dependency graph.

How do I detect GHSA-8629-vc8r-5p58 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for code.gitea.io/gitea. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-8629-vc8r-5p58 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-8629-vc8r-5p58?

O3 pinpoints whether GHSA-8629-vc8r-5p58 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-8629-vc8r-5p58 actively exploited in the wild?

No public exploit code has been indexed for GHSA-8629-vc8r-5p58 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-8629-vc8r-5p58?

GHSA-8629-vc8r-5p58 is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-8629-vc8r-5p58 published, and has it been updated?

GHSA-8629-vc8r-5p58 was published on June 16, 2026 and was last updated on June 25, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-8629-vc8r-5p58

MEDIUM

GHSA-8629-vc8r-5p58 is a medium-severity (CVSS 4.3) CWE-862 vulnerability in code.gitea.io/gitea. O3 Security confirms whether GHSA-8629-vc8r-5p58 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Gitea: Incomplete CVE-2025-68941 fix: /user/orgs missing checkTokenPublicOnly + switch-case logic flaw

Also known asCVE-2026-25714GO-2026-5243

Published

Jun 16, 2026

Updated

Jun 25, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🐹code.gitea.io/gitea

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Summary

Two related issues in the token public-only scope enforcement introduced by PR #32204 (CVE-2025-68941 fix). A public-only scoped API token can access private organization data.

Issue 1: /user/orgs missing checkTokenPublicOnly()

routers/api/v1/api.go line 1599:

m.Get("/user/orgs", reqToken(), tokenRequiresScopes(
    auth_model.AccessTokenScopeCategoryUser,
    auth_model.AccessTokenScopeCategoryOrganization,
), org.ListMyOrgs)
// Missing checkTokenPublicOnly()

Adjacent route at line 1603 has it:

m.Group("/users/{username}/orgs", func() { ... },
    ..., checkTokenPublicOnly())

Issue 2: checkTokenPublicOnly switch-case evaluates only first matching category

routers/api/v1/api.go lines 253-295. Go switch executes only the first matching case. For routes with categories [User, Organization]:

Organization case matches first (line 263)
ctx.Org.Organization is nil on user routes, passes
ctx.ContextUser.IsOrganization() is false, passes
User case (line 273) is never reached
User visibility check skipped entirely

Steps to Reproduce

Create a token with public-only scope (Settings > Applications > check "public only")
Call: curl -H "Authorization: token <PUBLIC_ONLY_TOKEN>" https://gitea.example.com/api/v1/user/orgs
Response includes private and limited-visibility organizations

Expected: only public organizations returned.

Impact

Public-only scoped tokens can enumerate private organizations the token owner belongs to. Violates the token's declared scope constraints.

Suggested Fix

Add checkTokenPublicOnly() to /user/orgs route at line 1599
Replace switch with loop over all categories so User visibility check is not skipped

Version

Current main branch, commit 2c2d7e6 (April 3, 2026).

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`code.gitea.io/gitea`	all versions	1.26.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for code.gitea.io/gitea. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update code.gitea.io/gitea to 1.26.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8629-vc8r-5p58 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-8629-vc8r-5p58 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-8629-vc8r-5p58. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary Two related issues in the token public-only scope enforcement introduced by PR #32204 (CVE-2025-68941 fix). A public-only scoped API token can access private organization data. ## Issue 1: /user/orgs missing checkTokenPublicOnly() `routers/api/v1/api.go` line 1599: ```go m.Get("/user/orgs", reqToken(), tokenRequiresScopes( auth_model.AccessTokenScopeCategoryUser, auth_model.AccessTokenScopeCategoryOrganization, ), org.ListMyOrgs) // Missing checkTokenPublicOnly() ``` Adjacent route at line 1603 has it: ```go m.Group("/users/{username}/orgs", func() { ... }, ..., chec

O3 Security · Impact-Aware SCA

Is GHSA-8629-vc8r-5p58 in your dependencies?

O3 detects GHSA-8629-vc8r-5p58 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works