# CVE-2026-123012: 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 di


- **Severity:** High 7.1 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 5 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-hqvj-j27r-9j7c

## What is CVE-2026-123012?

CVE-2026-123012 is a high-severity vulnerability in Gogs, published on 5 Nov 2026. 

### Official description

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.

Weakness: CWE-178 (Improper Handling of Case Sensitivity)

## Which versions are affected by CVE-2026-123012?


## How do I fix CVE-2026-123012?

No fix has been published for CVE-2026-123012 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-123012 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-123012 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-123012 and fix it if it is affected.

What it is: CVE-2026-123012 is a high-severity vulnerability in Gogs, published on 5 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-123012 exists.

Affected product: Gogs. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-123012/ (Markdown: https://insights.sbomify.com/CVE-2026-123012/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-123012
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-123012
- OSV: https://osv.dev/vulnerability/CVE-2026-123012

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-123012/
Summaries are generated and may contain mistakes; the official description above is the record.