CVE-2026-20779

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 62% 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
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 0

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

Gitea versions from 1.5.0 before 1.26.3 have a TOTP single-use enforcement defect that allows a valid TOTP code to be accepted more than once across web two-factor authentication flows and the Basic Auth X-Gitea-OTP path.

CVSS v3
7.1
EG Score
7.1(medium)
EPSS
38.1%
KEV
Not listed

Published

July 3, 2026

Last Modified

July 7, 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

TOTP TOCTOU race on web 2FA paths + missing replay check on Basic-Auth `X-Gitea-OTP` surface · Advisory · go-gitea/gitea · GitHub

https://github.com/go-gitea/gitea/security/advisories/GHSA-gx3v-q759-g323
github_release Patch Available

v1.26.3

Patch available: go-gitea/gitea v1.26.3

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

fix: Various security fixes (#38103)

Fix merged in go-gitea/gitea PR #38151 on 2026-06-17 — awaiting tagged release

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

Gitea 1.26.3 and 1.26.4 are released | Gitea Blog

https://blog.gitea.com/release-of-1.26.3-and-1.26.4/

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 21× 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.

  1. 2026-07-11 23:02 UTCEG score recompute
  2. 2026-07-11 11:00 UTCEG score recompute
  3. 2026-07-11 08:27 UTCEPSS rescore
  4. 2026-07-10 22:58 UTCEG score recompute
  5. 2026-07-10 10:57 UTCEG score recompute
  6. 2026-07-09 22:51 UTCEG score recompute
  7. 2026-07-09 19:10 UTCEPSS rescore
  8. 2026-07-09 10:50 UTCEG score recompute
  9. 2026-07-08 22:47 UTCEG score recompute
  10. 2026-07-08 15:15 UTCEPSS rescore
  11. 2026-07-08 15:15 UTCEPSS rescore
  12. 2026-07-08 10:46 UTCEG score recompute
  13. 2026-07-07 22:44 UTCEG score recompute
  14. 2026-07-07 13:46 UTCEPSS rescore
  15. 2026-07-07 10:44 UTCEG score recompute
  16. 2026-07-06 22:41 UTCEG score recompute
  17. 2026-07-06 10:40 UTCEG score recompute
  18. 2026-07-06 02:23 UTCEPSS rescore
  19. 2026-07-06 02:23 UTCEPSS rescore
  20. 2026-07-05 22:37 UTCEG score recompute
  21. 2026-07-05 10:36 UTCEG score recompute
  22. 2026-07-05 02:30 UTCEPSS rescore
  23. 2026-07-04 22:33 UTCEG score recompute
  24. 2026-07-04 10:31 UTCEG score recompute
  25. 2026-07-03 22:30 UTCEG score recompute
Show 1 more
  1. 2026-07-03 22:27 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-20779?
CVE-2026-20779 is a high vulnerability published on July 3, 2026. Gitea versions from 1.5.0 before 1.26.3 have a TOTP single-use enforcement defect that allows a valid TOTP code to be accepted more than once across web two-factor authentication flows and the Basic Auth X-Gitea-OTP path.
When was CVE-2026-20779 disclosed?
CVE-2026-20779 was first published in the National Vulnerability Database on July 3, 2026, with the most recent update on July 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-20779 actively exploited?
CVE-2026-20779 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 38.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-20779?
CVE-2026-20779 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-20779?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-20779, 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

Explore the affected products and dependency analysis for CVE-2026-20779

Explore →

Is Your Infrastructure Affected by CVE-2026-20779?

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

Start Free Scan →Browse All CVEs