Gogs is an open source self-hosted Git service. In versions 0.13.4 and below, the DeleteComment API does not verify that the comment belongs to the repository specified in the URL. This allows a repository administrator to delete comments from any other repository by supplying arbitrary comment IDs, bypassing authorization controls. The DeleteComment function retrieves a comment by ID without verifying repository ownership and the Database function DeleteCommentByID performs no repository validation. This issue has been fixed in version 0.14.0.
CVE-2026-25120
This low-severity CVE scores 2.7 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 81% 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).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 2.7
- EG Score
- 2.7(medium)
- EG Risk
- 17(Track)EG Risk 17/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 computedSeverity27% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 21%
- KEV
- Not listed
Published
February 19, 2026
Last Modified
June 17, 2026
References (2)
- security-advisories@githubhttps://github.com/gogs/gogs/commit/1b226ca48dc8b3e95cc1c41229d72819c960a1b7
- security-advisories@githubhttps://github.com/gogs/gogs/security/advisories/GHSA-jj5m-h57j-5gv7
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| gogs.io/gogs | — | 0.14.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× 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.
- 2026-09-18 19:27 UTCEPSS rescore
- 2026-09-17 13:50 UTCOSV refresh
- 2026-09-16 14:07 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-12 15:01 UTCEPSS rescore
- 2026-09-11 14:52 UTCEPSS rescore
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:11 UTCEPSS rescore
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 14:13 UTCOSV refresh
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 13:48 UTCEPSS rescore
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
Show 27 moreShow fewer
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 01:53 UTCEG score recompute
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-09 13:59 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 03:30 UTCEG score recompute
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 20:13 UTCEG score recompute
- 2026-08-02 02:26 UTCEPSS rescore
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:27 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-27 13:27 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
- CVE-2018-25270EG 9.8CRITICAL
- CVE-2017-20223EG 9.8CRITICAL
- CVE-2019-25487EG 9.8EPSS p94CRITICAL
- CVE-2019-25235EG 9.8CRITICAL
- CVE-2019-15310EG 9.8EPSS p95CRITICAL
- CVE-2019-15913EG 9.8CRITICAL
- CVE-2019-16340EG 9.8EPSS p97CRITICAL
- CVE-2019-13360EG 9.8EPSS p98CRITICAL
- CVE-2019-12866EG 9.8CRITICAL
- CVE-2019-9756EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-25120?
When was CVE-2026-25120 disclosed?
Is CVE-2026-25120 actively exploited?
What is the CVSS score of CVE-2026-25120?
How do I remediate CVE-2026-25120?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-25120
Is Your Infrastructure Affected by CVE-2026-25120?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.