CVE-2026-25718

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
9.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.1Exploit: NoneExposed: 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 mishandle path resolution during template repository generation, allowing template processing to read or write through symlinked or otherwise non-regular paths.

CVSS v3
9.1
EG Score
9.1(high)
EG Risk
56(Track)
EG Risk 56/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
Severity91% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
35.0%
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.
generic

Gitea 1.25.5 is released | Gitea Blog

https://blog.gitea.com/release-of-1.25.5/
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 path resolving (#36734)

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

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

Fix path resolving

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

https://github.com/go-gitea/gitea/pull/36734

Vendor Advisories for CVE-2026-25718(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 14× in last 7d / 84× 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-23 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:07 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-22 14:08 UTCEPSS rescore
  6. 2026-07-21 15:24 UTCEPSS rescore
  7. 2026-07-21 15:24 UTCEPSS rescore
  8. 2026-07-20 17:08 UTCEPSS rescore
  9. 2026-07-19 14:31 UTCEPSS rescore
  10. 2026-07-19 14:31 UTCEPSS rescore
  11. 2026-07-19 02:29 UTCEPSS rescore
  12. 2026-07-19 02:28 UTCEPSS rescore
  13. 2026-07-18 10:04 UTCEPSS rescore
  14. 2026-07-18 10:04 UTCEPSS rescore
  15. 2026-07-17 03:07 UTCGHSA enrichment
  16. 2026-07-16 22:54 UTCGHSA enrichment
  17. 2026-07-16 18:40 UTCGHSA enrichment
  18. 2026-07-16 17:03 UTCEPSS rescore
  19. 2026-07-16 17:03 UTCEPSS rescore
  20. 2026-07-16 14:26 UTCGHSA enrichment
  21. 2026-07-16 10:09 UTCGHSA enrichment
  22. 2026-07-16 05:55 UTCGHSA enrichment
  23. 2026-07-16 01:42 UTCGHSA enrichment
  24. 2026-07-15 21:28 UTCGHSA enrichment
  25. 2026-07-15 17:14 UTCGHSA enrichment
Show 59 more
  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 12:59 UTCGHSA enrichment
  4. 2026-07-15 08:41 UTCGHSA enrichment
  5. 2026-07-15 04:28 UTCGHSA enrichment
  6. 2026-07-15 02:00 UTCEPSS rescore
  7. 2026-07-15 02:00 UTCEPSS rescore
  8. 2026-07-15 00:10 UTCGHSA enrichment
  9. 2026-07-14 19:56 UTCGHSA enrichment
  10. 2026-07-14 15:43 UTCGHSA enrichment
  11. 2026-07-14 11:29 UTCGHSA enrichment
  12. 2026-07-14 07:16 UTCGHSA enrichment
  13. 2026-07-14 03:02 UTCGHSA enrichment
  14. 2026-07-13 22:49 UTCGHSA enrichment
  15. 2026-07-13 22:30 UTCEPSS rescore
  16. 2026-07-13 18:35 UTCGHSA enrichment
  17. 2026-07-13 14:21 UTCGHSA enrichment
  18. 2026-07-13 10:07 UTCGHSA enrichment
  19. 2026-07-13 06:13 UTCEPSS rescore
  20. 2026-07-13 06:13 UTCEPSS rescore
  21. 2026-07-13 05:53 UTCGHSA enrichment
  22. 2026-07-13 01:40 UTCGHSA enrichment
  23. 2026-07-12 21:27 UTCGHSA enrichment
  24. 2026-07-12 17:13 UTCGHSA enrichment
  25. 2026-07-12 12:59 UTCGHSA enrichment
  26. 2026-07-12 08:46 UTCGHSA enrichment
  27. 2026-07-12 05:46 UTCEPSS rescore
  28. 2026-07-12 05:46 UTCEPSS rescore
  29. 2026-07-12 04:31 UTCGHSA enrichment
  30. 2026-07-12 00:17 UTCGHSA enrichment
  31. 2026-07-11 20:04 UTCGHSA enrichment
  32. 2026-07-11 15:49 UTCGHSA enrichment
  33. 2026-07-11 11:36 UTCGHSA enrichment
  34. 2026-07-11 08:27 UTCEPSS rescore
  35. 2026-07-11 07:22 UTCGHSA enrichment
  36. 2026-07-11 03:08 UTCGHSA enrichment
  37. 2026-07-10 22:54 UTCGHSA enrichment
  38. 2026-07-10 18:41 UTCGHSA enrichment
  39. 2026-07-10 14:28 UTCGHSA enrichment
  40. 2026-07-10 10:15 UTCGHSA enrichment
  41. 2026-07-10 06:01 UTCGHSA enrichment
  42. 2026-07-10 01:47 UTCGHSA enrichment
  43. 2026-07-09 21:34 UTCGHSA enrichment
  44. 2026-07-09 19:10 UTCEPSS rescore
  45. 2026-07-09 17:21 UTCGHSA enrichment
  46. 2026-07-09 13:06 UTCEG score recompute▲ 9.10
  47. 2026-07-09 13:06 UTCGHSA enrichment
  48. 2026-07-08 15:15 UTCEPSS rescore
  49. 2026-07-08 15:15 UTCEPSS rescore
  50. 2026-07-07 17:31 UTCMITRE cvelistV5CVSS v3 → 9.1 · severity → CRITICAL
  51. 2026-07-07 13:46 UTCEPSS rescore
  52. 2026-07-06 17:48 UTCGHSA enrichment
  53. 2026-07-06 16:27 UTCEPSS rescore
  54. 2026-07-06 16:27 UTCEPSS rescore
  55. 2026-07-06 02:23 UTCEPSS rescore
  56. 2026-07-06 02:23 UTCEPSS rescore
  57. 2026-07-05 02:30 UTCEPSS rescore
  58. 2026-07-03 22:29 UTCEG score recompute
  59. 2026-07-03 22:29 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-25718?
CVE-2026-25718 is a critical vulnerability published on July 3, 2026. Gitea versions before 1.25.5 mishandle path resolution during template repository generation, allowing template processing to read or write through symlinked or otherwise non-regular paths.
When was CVE-2026-25718 disclosed?
CVE-2026-25718 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-25718 actively exploited?
CVE-2026-25718 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 35.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-25718?
CVE-2026-25718 has a CVSS v3.1 base score of 9.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-25718?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-25718, 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-25718

Explore →

Is Your Infrastructure Affected by CVE-2026-25718?

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

Start Free Scan →Browse All CVEs