CVE-2026-20909

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory published 2026-07-03. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

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

Gitea versions before 1.25.5 have insufficient permission checks when listing tracked time entries.

CVSS v3
5.3
EG Score
5.3(high)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
21%
KEV
Not listed

Published

July 3, 2026

Last Modified

July 7, 2026

Advisory Details (4)

Auto-updated Jul 7, 2026
Patch available. Sources: github_pr, github_release.
github_release Patch Available

v1.25.5

Patch available: go-gitea/gitea v1.25.5

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

Fix track time list permission check (#36662)

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

https://github.com/go-gitea/gitea/pull/36744
github_pr

Fix track time list permission check

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

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

Gitea 1.25.5 is released | Gitea Blog

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

Vendor Advisories for CVE-2026-20909(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 65× 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-30 04:06 UTCEG score recompute
  2. 2026-07-30 04:06 UTCGHSA enrichment
  3. 2026-07-30 01:30 UTCEPSS rescore
  4. 2026-07-29 06:21 UTCEG score recompute
  5. 2026-07-29 06:21 UTCGHSA enrichment
  6. 2026-07-28 08:31 UTCEG score recompute
  7. 2026-07-28 08:31 UTCGHSA enrichment
  8. 2026-07-27 14:13 UTCEPSS rescore
  9. 2026-07-27 10:43 UTCEG score recompute
  10. 2026-07-27 10:43 UTCGHSA enrichment
  11. 2026-07-26 14:54 UTCEPSS rescore
  12. 2026-07-26 14:54 UTCEPSS rescore
  13. 2026-07-26 12:55 UTCEG score recompute
  14. 2026-07-26 12:55 UTCGHSA enrichment
  15. 2026-07-25 14:17 UTCEPSS rescore
  16. 2026-07-25 14:17 UTCEPSS rescore
  17. 2026-07-24 14:17 UTCEPSS rescore
  18. 2026-07-23 14:18 UTCEPSS rescore
  19. 2026-07-23 14:18 UTCEPSS rescore
  20. 2026-07-23 03:06 UTCEG score recompute
  21. 2026-07-22 14:08 UTCEPSS rescore
  22. 2026-07-21 15:24 UTCEPSS rescore
  23. 2026-07-21 15:24 UTCEPSS rescore
  24. 2026-07-20 17:08 UTCEPSS rescore
  25. 2026-07-19 14:31 UTCEPSS rescore
Show 40 more
  1. 2026-07-19 14:31 UTCEPSS rescore
  2. 2026-07-19 02:29 UTCEPSS rescore
  3. 2026-07-19 02:28 UTCEPSS rescore
  4. 2026-07-18 10:04 UTCEPSS rescore
  5. 2026-07-18 10:04 UTCEPSS rescore
  6. 2026-07-16 17:42 UTCGHSA enrichment
  7. 2026-07-16 17:03 UTCEPSS rescore
  8. 2026-07-16 17:03 UTCEPSS rescore
  9. 2026-07-15 19:57 UTCGHSA enrichment
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 16:57 UTCEPSS rescore
  12. 2026-07-15 02:00 UTCEPSS rescore
  13. 2026-07-15 02:00 UTCEPSS rescore
  14. 2026-07-14 22:12 UTCGHSA enrichment
  15. 2026-07-14 00:27 UTCGHSA enrichment
  16. 2026-07-13 22:30 UTCEPSS rescore
  17. 2026-07-13 06:13 UTCEPSS rescore
  18. 2026-07-13 06:13 UTCEPSS rescore
  19. 2026-07-13 02:42 UTCGHSA enrichment
  20. 2026-07-12 05:46 UTCEPSS rescore
  21. 2026-07-12 05:46 UTCEPSS rescore
  22. 2026-07-12 04:57 UTCGHSA enrichment
  23. 2026-07-11 08:27 UTCEPSS rescore
  24. 2026-07-11 07:12 UTCGHSA enrichment
  25. 2026-07-10 09:26 UTCGHSA enrichment
  26. 2026-07-09 19:10 UTCEPSS rescore
  27. 2026-07-09 11:37 UTCEG score recompute▲ 5.30
  28. 2026-07-09 11:37 UTCGHSA enrichment
  29. 2026-07-08 15:15 UTCEPSS rescore
  30. 2026-07-08 15:15 UTCEPSS rescore
  31. 2026-07-07 17:31 UTCMITRE cvelistV5CVSS v3 → 5.3 · severity → MEDIUM
  32. 2026-07-07 13:46 UTCEPSS rescore
  33. 2026-07-06 17:04 UTCGHSA enrichment
  34. 2026-07-06 16:27 UTCEPSS rescore
  35. 2026-07-06 16:27 UTCEPSS rescore
  36. 2026-07-06 02:23 UTCEPSS rescore
  37. 2026-07-06 02:23 UTCEPSS rescore
  38. 2026-07-05 02:30 UTCEPSS rescore
  39. 2026-07-03 22:29 UTCEG score recompute
  40. 2026-07-03 22:29 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-20909?
CVE-2026-20909 is a medium vulnerability published on July 3, 2026. Gitea versions before 1.25.5 have insufficient permission checks when listing tracked time entries.
When was CVE-2026-20909 disclosed?
CVE-2026-20909 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-20909 actively exploited?
CVE-2026-20909 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 79.1% of all scored CVEs.
What is the CVSS score of CVE-2026-20909?
CVE-2026-20909 has a CVSS v3.1 base score of 5.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-20909?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-20909, 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-20909

Explore →

Is Your Infrastructure Affected by CVE-2026-20909?

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

Start Free Scan →Browse All CVEs