Gitea versions up to and including 1.26.1 do not apply public-only token filtering consistently to the user organization API, leaving an incomplete fix for CVE-2025-68941.
CVE-2026-25714
This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 81% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.3
- EG Score
- 4.3(medium)
- EPSS
- 18.8%
- KEV
- Not listed
Published
June 16, 2026
Last Modified
July 7, 2026
Advisory Details (4)
Auto-updated Jul 3, 2026Incomplete CVE-2025-68941 fix: /user/orgs missing checkTokenPublicOnly + switch-case logic flaw · Advisory · go-gitea/gitea · GitHub
https://github.com/go-gitea/gitea/security/advisories/GHSA-8629-vc8r-5p58v1.26.2
Patch available: go-gitea/gitea v1.26.2
https://github.com/go-gitea/gitea/releases/tag/v1.26.2fix: Unify public-only token filtering in API queries and repo access checks
Fix merged in go-gitea/gitea PR #37118 on 2026-05-18 — awaiting tagged release
https://github.com/go-gitea/gitea/pull/37118Vendor Advisories for CVE-2026-25714(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| code.gitea.io/gitea | — | 1.26.2 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 26× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-08 00:41 UTCEG score recompute
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 22:51 UTCEG score recompute
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 10:49 UTCEG score recompute
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 08:59 UTCEG score recompute
- 2026-07-03 03:59 UTCEG score recompute
- 2026-07-02 02:05 UTCEG score recompute
- 2026-07-01 00:14 UTCEG score recompute
- 2026-06-29 22:23 UTCEG score recompute
- 2026-06-28 20:33 UTCEG score recompute
- 2026-06-27 18:43 UTCEG score recompute
- 2026-06-26 16:52 UTCEG score recompute
- 2026-06-25 15:02 UTCEG score recompute
- 2026-06-24 13:11 UTCEG score recompute
- 2026-06-23 11:12 UTCEG score recompute
- 2026-06-22 09:18 UTCEG score recompute
- 2026-06-21 07:24 UTCEG score recompute
- 2026-06-20 05:25 UTCEG score recompute
- 2026-06-19 03:24 UTCEG score recompute
- 2026-06-18 01:33 UTCEG score recompute
Show 1 moreShow fewer
- 2026-06-16 23:43 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-862
Frequently asked(5)
What is CVE-2026-25714?
When was CVE-2026-25714 disclosed?
Is CVE-2026-25714 actively exploited?
What is the CVSS score of CVE-2026-25714?
How do I remediate CVE-2026-25714?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-25714
Is Your Infrastructure Affected by CVE-2026-25714?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.