Gitea versions before 1.25.5 have insufficient visibility checks in organization permission APIs for hidden members and private organizations.
CVE-2026-25712
HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence
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.
Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0
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(medium)
- 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
- 41%
- KEV
- Not listed
Published
July 3, 2026
Last Modified
July 7, 2026
Advisory Details (4)
Auto-updated Jul 7, 2026Patch 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.5github_pr
Fix org permission API visibility checks for hidden members and private orgs (#36798)
Fix merged in go-gitea/gitea PR #36841 on 2026-03-08 — awaiting tagged release
https://github.com/go-gitea/gitea/pull/36841github_pr
Fix org permission API visibility checks for hidden members and private orgs
Fix merged in go-gitea/gitea PR #36798 on 2026-03-06 — awaiting tagged release
https://github.com/go-gitea/gitea/pull/36798Vendor Advisories for CVE-2026-25712(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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| code.gitea.io/gitea | — | 1.25.5 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Frequently asked(5)
What is CVE-2026-25712?
CVE-2026-25712 is a high vulnerability published on July 3, 2026. Gitea versions before 1.25.5 have insufficient visibility checks in organization permission APIs for hidden members and private organizations.
When was CVE-2026-25712 disclosed?
CVE-2026-25712 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-25712 actively exploited?
CVE-2026-25712 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 59.4% of all scored CVEs.
What is the CVSS score of CVE-2026-25712?
CVE-2026-25712 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-25712?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-25712, 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-25712
Is Your Infrastructure Affected by CVE-2026-25712?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.