CVE-2026-123012
HIGHDescription
In Gogs 0.14.3, the Git Smart HTTP authorization layer in internal/route/repo/http.go allows a push when only read access was intended, a different vulnerability than CVE-2026-52810. This occurs because of a case-sensitivity desync between the authorization classifier and the request dispatcher: the gitHTTPIsPull function compares the Git action verb case-sensitively and defaults to pull (read access) for any unrecognized string, whereas the request dispatcher lowercases the same verb before routing it to the receive-pack handler. Capitalizing a single letter in the URL (e.g. info/Refs instead of info/refs, or git-receive-Pack instead of git-receive-pack) causes the classifier to misidentify a push as a pull, granting only read-level authorization, whereas the dispatcher routes it to the write handler. An authenticated read-only collaborator can exploit this to push to a private repository, creating, updating, or deleting refs.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v4 Vector
Exploitability
Impact
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Exploit Intelligence
Low risk: more likely to be exploited than 27% of all known CVEs.
References
Related Vulnerabilities
Other CWE-178 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2025-27636 | Medium | 5.6 | 97% | - | Fix |
| CVE-2021-24347 | High | 8.8 | 54% | - | Fix |
| CVE-2020-12812 | Critical | 9.8 | 45% | KEV + Ransom | Fix |
| CVE-2003-0411 | High | 7.5 | 25% | - | - |
| CVE-2026-47323 | Critical | 9.8 | 20% | - | Fix |
| CVE-2018-9845 | Critical | 9.8 | 13% | - | Fix |
Common questions
How do I fix CVE-2026-123012?
No published fix for CVE-2026-123012 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-123012 being actively exploited?
Not that we know of. CVE-2026-123012 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.34% is the estimated probability that it will be exploited in the next 30 days. That is higher than 27% of all scored CVEs.
How severe is CVE-2026-123012?
CVE-2026-123012 has a CVSS v4 base score of 7.1, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-123012
Markdown
[](https://tridentstack.com/cve/CVE-2026-123012)HTML
<a href="https://tridentstack.com/cve/CVE-2026-123012"><img src="https://tridentstack.com/cve/badge/CVE-2026-123012.svg" alt="CVE-2026-123012"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-11-12.