Gitea versions before 1.25.5 have insufficient permission checks for updating or rebasing pull request branches.
CVE-2026-24690
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-03. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 49(Track)EG Risk 49/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 computedSeverity75% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 25%
- KEV
- Not listed
Published
July 3, 2026
Last Modified
July 7, 2026
Advisory Details (4)
Auto-updated Jul 7, 2026v1.25.5
Patch available: go-gitea/gitea v1.25.5
https://github.com/go-gitea/gitea/releases/tag/v1.25.5Fix bug to check whether user can update pull request branch or rebase branch (#36465)
Fix merged in go-gitea/gitea PR #36838 on 2026-03-08 — awaiting tagged release
https://github.com/go-gitea/gitea/pull/36838Fix bug to check whether user can update pull request branch or rebase branch
Fix merged in go-gitea/gitea PR #36465 on 2026-03-05 — awaiting tagged release
https://github.com/go-gitea/gitea/pull/36465Vendor Advisories for CVE-2026-24690(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 22× in last 7d / 78× 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-30 16:27 UTCEPSS rescore
- 2026-07-30 12:16 UTCEG score recompute
- 2026-07-30 12:16 UTCGHSA enrichment
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-30 00:07 UTCGHSA enrichment
- 2026-07-29 12:26 UTCGHSA enrichment
- 2026-07-29 00:44 UTCEG score recompute
- 2026-07-29 00:44 UTCGHSA enrichment
- 2026-07-28 13:02 UTCGHSA enrichment
- 2026-07-28 00:46 UTCEG score recompute
- 2026-07-28 00:46 UTCGHSA enrichment
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-27 12:33 UTCGHSA enrichment
- 2026-07-27 00:52 UTCEG score recompute
- 2026-07-27 00:52 UTCGHSA enrichment
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 12:55 UTCEG score recompute
- 2026-07-26 12:55 UTCGHSA enrichment
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:07 UTCEG score recompute
Show 53 moreShow fewer
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-19 02:28 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-17 00:13 UTCGHSA enrichment
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-16 12:32 UTCGHSA enrichment
- 2026-07-16 00:51 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 13:10 UTCGHSA enrichment
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 01:28 UTCGHSA enrichment
- 2026-07-14 13:47 UTCGHSA enrichment
- 2026-07-14 02:06 UTCGHSA enrichment
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 14:25 UTCGHSA enrichment
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 02:42 UTCGHSA enrichment
- 2026-07-12 15:01 UTCGHSA enrichment
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 03:20 UTCGHSA enrichment
- 2026-07-11 15:38 UTCGHSA enrichment
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 03:56 UTCGHSA enrichment
- 2026-07-10 16:15 UTCGHSA enrichment
- 2026-07-10 04:23 UTCGHSA enrichment
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 16:40 UTCEG score recompute▲ 7.50
- 2026-07-09 16:40 UTCGHSA enrichment
- 2026-07-08 15:15 UTCEPSS rescore
- 2026-07-08 15:15 UTCEPSS rescore
- 2026-07-07 17:31 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 19:37 UTCGHSA enrichment
- 2026-07-06 19:35 UTCGHSA enrichment
- 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 02:30 UTCEPSS rescore
- 2026-07-03 22:30 UTCEG score recompute
- 2026-07-03 22:29 UTCGHSA enrichment
Related CVEs(same CWE)
Same CWE
10 shownCWE-284
Frequently asked(5)
What is CVE-2026-24690?
When was CVE-2026-24690 disclosed?
Is CVE-2026-24690 actively exploited?
What is the CVSS score of CVE-2026-24690?
How do I remediate CVE-2026-24690?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-24690
Is Your Infrastructure Affected by CVE-2026-24690?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.