Gogs branch protection bypass in pull request merge
- Exploited
- Proof of concept public, per CISA
- Fix
- Fix or patch referenced
- Who is exposed
- Specific setups only
Summary
Gogs contains an authorization bypass that lets a remote attacker with low-privilege login, such as a collaborator with write access, merge pull requests to push commits into protected branches restricted to allowlisted users. The flaw exists because the pull request merge process skips branch protection checks.
Written by a model
Original description
Gogs through 0.14.4 contains an authorization bypass vulnerability that allows collaborators with write access to push to protected branches by merging pull requests. Because MergePullRequest skips branch protection checks and PullRequest.Merge omits hook environment variables, attackers can merge commits into branches restricted to allowlisted users.
Who should check
Teams self-hosting Gogs through 0.14.4 that rely on protected branch push whitelists or required code review on release branches.
“Affecting gogs <= 0.14.4”
What to do
Check whether your setup matches what the bug needs.
Gogs versions through 0.14.4 (affected range given as <= 0.14.4; the GHSA lists < 0.15.0). The target branch is protected with a push whitelist enabled, and the attacker is not on that whitelist. The attacker is a repository collaborator with Write access.Apply the patch listed under Evidence.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133113 (Gogs through 0.14.4 Protected Branch Allowlist Bypass via Pull Request Merge), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133113 (entry last updated 2026-11-19):
Affected:
- Go package gogs.io/gogs: through 0.14.4
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Gogs versions through 0.14.4 (affected range given as <= 0.14.4; the GHSA lists < 0.15.0). (source: https://www.vulncheck.com/advisories/gogs-through-0.14.4-protected-branch-allowlist-bypass-via-pull-request-merge)
- The target branch is protected with a push whitelist enabled, and the attacker is not on that whitelist. (source: https://github.com/gogs/gogs/security/advisories/GHSA-8r2x-49gj-h6rm)
- The attacker is a repository collaborator with Write access. (source: https://github.com/gogs/gogs/security/advisories/GHSA-8r2x-49gj-h6rm)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-133113 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133113 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/gogs/gogs/security/advisories/GHSA-8r2x-49gj-h6rm
- https://github.com/gogs/gogs/commit/089f089fa783f95b54a635b8ec9b3f498c2a5d12
- https://github.com/gogs/gogs/commit/1651767a3e2c531ccf0af2141d691cfff8763e09
- https://github.com/gogs/gogs/blob/v0.14.4/internal/route/repo/pull.go#L401-L431
- https://github.com/gogs/gogs
- https://www.vulncheck.com/advisories/gogs-through-0.14.4-protected-branch-allowlist-bypass-via-pull-request-merge
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133113
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133113"}.Affected versions
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- 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 47 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Evidence 9
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · gogs/gogs · Advisory GHSA-8r2x-49gj-h6rm |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133113 |
| Record | NVD · CVE-2026-133113 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | GitHub · LLCForge/CVE-2026-133113 · Repository |
| Other links 5 | |
| Patch | GitHub · gogs/gogs · Commit 089f089f |
| Patch | GitHub · gogs/gogs · Commit 1651767a |
| Repository | GitHub · gogs/gogs · internal/route/repo/pull.go · L401-L431 |
| Repository | GitHub · gogs/gogs · Repository |
| Link | vulncheck.com · advisories/gogs-through-0.14.4-protected-branch-allowlist-bypass-via-pull-request-merge |
Questions about CVE-2026-133113
Is CVE-2026-133113 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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
A collaborator with Write access can merge a pull request into a protected branch that is restricted to an allowlist of users. This bypasses the push whitelist and related review controls on that branch.
Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-133113?
gogs.io/gogs (Go): through 0.14.4.
Source: cve.now feed data
Am I affected, and how do I check?
Gogs versions through 0.14.4 are listed as affected, though the GHSA lists versions below 0.15.0. To check a installation, look at the Gogs version and whether the branch has push whitelist enabled in its protected branch settings.
Source: vulncheck.com, github.com
How do I fix CVE-2026-133113?
The checked facts name no fixed version and no patch ids, so no upgrade target is given here. Check the advisory for a fixed release before changing anything.
Source: vulncheck.com, github.com
Related
- CVE-2026-52813Gogs: Path Traversal in organization name results in RCE through Git hooks
- CVE-2026-52806Gogs: RCE via git rebase --exec argument injection in pull request merge
- CVE-2026-52798Gogs: Stored XSS in `.ipynb` Preview
- CVE-2026-52800Gogs: CSRF Leading to Organization Owner Takeover
- CVE-2026-52797Gogs: Overwriting critical files results in a denial of service
- CVE-2026-47267Gogs: SSRF in webhook deliveries
No corrections so far. Something wrong on this page? Report an error.