CVE-2026-28699 json
Gitea Basic Auth bypasses OAuth2 access token scopes
published 2026-06-16 4 mo ago modified 2026-10-25 14 d ago also GHSA-9r5x-wg6m-x2rc , GO-2026-5299 , EUVD-2026-41640
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 46%
- public exploits
- 0
- none known
Summary
Gitea versions up to and including 1.26.1 allow OAuth2 access token scope enforcement to be bypassed through HTTP Basic authentication.
Patch / fix
- go code.gitea.io/gitea 1.26.2
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
opensuse advisories openSUSE-SU-2026:21483-1
- github.com/go-gitea/gitea#37503 pull request
- github.com/go-gitea/gitea/releases/tag/v1.26.2 release
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 4 mo ago
Exploit prediction
0.55% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/go-gitea/gitea/security/advisories/GHSA-9r5x-wg6m-x2rc referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N |
| GitHub | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | code.gitea.io/gitea | <1.26.2 |
1.26.2 |
Affected products
- Gitea Gitea Open Source Git Server
Classification
References
-
github.com
/go-gitea/gitea/pull/37503
patch
-
github.com
/go-gitea/gitea/security/advisories/GHSA-9r5x-wg6m-x2rc
vendor-advisory, exploit, web, advisory
-
github.com
/go-gitea/gitea/releases/tag/v1.26.2
release-notes
-
blog.gitea.com
/release-of-1.26.2/
release-notes
-
github.com
/go-gitea/gitea
package
Sources
- CVE List CVE-2026-28699
- GitHub Advisory GHSA-9r5x-wg6m-x2rc
- NVD CVE-2026-28699
- OSV GO-2026-5299
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.