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…
Affects Gogs versions before 0.14.3, where a collaborator with only read access can push to repositories over Git Smart HTTP. Fixed in 0.14.3.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.14.3
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Gogs 0.14.3 (affected versions below 0.14.3) Attacker must hold read-only collaborator access to the repository, or the instance must have REQUIRE_SIGNIN_VIEW = true
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.33% · 25th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 25/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Gogs, a self-hosted Git service, has a flaw in its Git Smart HTTP authorization that lets a user with only read access push changes to a repository over the network. The attacker needs low-privilege login, and no user action is required.
Read the original 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 inconsistency about whether a verb is checked in a case-sensitive manner.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Affects Go packages
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 32 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Gogs 0.14.3 (affected versions below 0.14.3) Attacker must hold read-only collaborator access to the repository, or the instance must have REQUIRE_SIGNIN_VIEW = trueUpgrade to a fixed version: 0.14.3.
Workaround: Disable Git Smart HTTP access (set DISABLE_HTTP_GIT = true in app.ini) and use SSH-only for Git operations
Timeline
- CVE published
- Record last updated
- First seen by cve.now
Affected versions
- Gogs Gogs
0.14.3
- gogs.io/gogsGo
All versions
- gogs.io/gogsGo
fixed in 0.14.3
Evidence 4
- Advisory
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123012
Is CVE-2026-123012 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A collaborator who only has read access can push to a repository over Git Smart HTTP, although that access was meant to be read-only. Force pushes can overwrite existing branches such as main, which affects availability.Source: github.com
Which versions are affected by CVE-2026-123012?
Gogs: version 0.14.3. gogs.io/gogs (Go): all versions. gogs.io/gogs (Go): before 0.14.3.Source: cve.now feed data
Am I affected, and how do I check?
Gogs versions before 0.14.3 are affected. The exposed setup involves a collaborator with read-only access to the repository, or an instance where REQUIRE_SIGNIN_VIEW is not set to true in app.ini. Check the installed Gogs version and the app.ini settings to see which applies.Source: github.com
How do I fix CVE-2026-123012?
Upgrade to Gogs 0.14.3 or later. Until the upgrade is done, the workaround is to set DISABLE_HTTP_GIT = true in app.ini and use SSH-only for Git operations.Source: github.com