CVE-2026-28699

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 57% 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 8.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Gitea versions up to and including 1.26.1 allow OAuth2 access token scope enforcement to be bypassed through HTTP Basic authentication.

CVSS v3
8.1
EG Score
8.1(medium)
EPSS
42.9%
KEV
Not listed

Published

June 16, 2026

Last Modified

July 6, 2026

Advisory Details (4)

Auto-updated Jul 3, 2026
🔬 Proof of concept available. Patch available. Sources: github_pr, github_release, github.
github Patch Available🟡 PoC Available

OAuth2 access token scope enforcement bypass via HTTP Basic authentication · Advisory · go-gitea/gitea · GitHub

https://github.com/go-gitea/gitea/security/advisories/GHSA-9r5x-wg6m-x2rc
github_release Patch Available

v1.26.2

Patch available: go-gitea/gitea v1.26.2

https://github.com/go-gitea/gitea/releases/tag/v1.26.2
github_pr

Fix basic auth bug

Fix merged in go-gitea/gitea PR #37503 on 2026-05-02 — awaiting tagged release

https://github.com/go-gitea/gitea/pull/37503
generic

Gitea 1.26.2 is released | Gitea Blog

https://blog.gitea.com/release-of-1.26.2/

Vendor Advisories for CVE-2026-28699(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)
PackageVulnerable rangeFixed inDependents
code.gitea.io/gitea—1.26.2—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 17× in last 7d / 43× 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.

  1. 2026-07-06 22:55 UTCEG score recompute
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-05 22:47 UTCEG score recompute
  7. 2026-07-05 10:15 UTCEG score recompute
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-04 21:31 UTCEG score recompute
  10. 2026-07-04 08:59 UTCEG score recompute
  11. 2026-07-03 19:36 UTCEG score recompute
  12. 2026-07-03 07:06 UTCEG score recompute
  13. 2026-07-02 18:33 UTCEG score recompute
  14. 2026-07-02 06:01 UTCEG score recompute
  15. 2026-07-01 17:30 UTCEG score recompute
  16. 2026-07-01 04:57 UTCEG score recompute
  17. 2026-06-30 16:15 UTCEG score recompute
  18. 2026-06-30 03:43 UTCEG score recompute
  19. 2026-06-29 15:07 UTCEG score recompute
  20. 2026-06-29 02:33 UTCEG score recompute
  21. 2026-06-28 13:59 UTCEG score recompute
  22. 2026-06-28 01:29 UTCEG score recompute
  23. 2026-06-27 12:58 UTCEG score recompute
  24. 2026-06-27 00:26 UTCEG score recompute
  25. 2026-06-26 11:48 UTCEG score recompute
Show 18 more
  1. 2026-06-25 22:22 UTCEG score recompute
  2. 2026-06-25 09:50 UTCEG score recompute
  3. 2026-06-24 21:19 UTCEG score recompute
  4. 2026-06-24 08:48 UTCEG score recompute
  5. 2026-06-23 20:16 UTCEG score recompute
  6. 2026-06-23 07:28 UTCEG score recompute
  7. 2026-06-22 18:20 UTCEG score recompute
  8. 2026-06-22 05:50 UTCEG score recompute
  9. 2026-06-21 17:17 UTCEG score recompute
  10. 2026-06-21 04:30 UTCEG score recompute
  11. 2026-06-20 15:51 UTCEG score recompute
  12. 2026-06-20 03:18 UTCEG score recompute
  13. 2026-06-19 14:37 UTCEG score recompute
  14. 2026-06-19 02:05 UTCEG score recompute
  15. 2026-06-18 13:28 UTCEG score recompute
  16. 2026-06-18 00:54 UTCEG score recompute
  17. 2026-06-17 12:16 UTCEG score recompute
  18. 2026-06-16 23:44 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-28699?
CVE-2026-28699 is a high vulnerability published on June 16, 2026. Gitea versions up to and including 1.26.1 allow OAuth2 access token scope enforcement to be bypassed through HTTP Basic authentication.
When was CVE-2026-28699 disclosed?
CVE-2026-28699 was first published in the National Vulnerability Database on June 16, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-28699 actively exploited?
CVE-2026-28699 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 42.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-28699?
CVE-2026-28699 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-28699?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-28699, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-28699

Explore →

Is Your Infrastructure Affected by CVE-2026-28699?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs