Gogs security advisories published on November 18, 2026 describe four different failures in repository protection, account authentication and commit rendering. Operators should compare their running build and configuration against each row before planning a change. The vulnerability intelligence platform can help organize the resulting exposure and remediation decisions.
The four advisories do not share one fix state. One lists no patched version, two name a development build, and one lists 0.15.0 even though the Gogs releases page currently identifies v0.14.4 as its latest tagged release. Treat an advisory’s “patched versions” field as a claim about that build, not proof that a stable download is available.
Gogs Security Advisories: Exposure and Fix Matrix
| Advisory and condition | Affected version | Fix status stated by the advisory |
|---|---|---|
| Protected branch bypass: a collaborator has Write access and merges a pull request into a protected branch. | Before 0.15.0; the report tested 0.14.3. | “None” is listed under patched versions. No published fix is established by this advisory. |
| Two-factor web API bypass: an attacker knows an account password; the account has two-factor authentication enabled. | 0.15.0+dev, including the reported main-branch build. | 0.15.0+dev is also listed as patched. This is a development-branch label, not a stable release number. |
| LDAP identity mismatch: LDAP is configured; a controlled directory entry can match another LDAP user’s Gogs email. | Before 0.15.0; the report tested 0.14.4. | 0.15.0 is listed as patched. Verify an actual release and its contents before scheduling an upgrade. |
| Stored cross-site scripting: a repository admin controls an external issue-tracker format, and a visitor clicks a rendered issue reference. | 0.15.0+dev. | 0.15.0+dev is listed as patched; the advisory does not identify a stable release containing the fix. |
These version labels describe different code lines. The two development-only reports should not be projected backward onto every 0.14 deployment. Conversely, the 0.14 branch and LDAP rows should not be closed merely because a development advisory uses the word “patched.”
How Do the Four Failures Change Security Decisions?
The branch-protection report traces a gap between the web merge action and the pre-receive hook. During a pull request merge, an internal Git push lacks the environment value that enables the hook’s protection checks. A Write collaborator can therefore merge into a protected branch despite a push whitelist or required review condition, according to the report.
For maintainers, the immediate question is whether a protected branch depends on Gogs merge controls as its sole gate. Until a verified fix exists, restrict merge permission to people authorized for the protected branch and review recent merges by users outside its intended approval set. This is our interim control based on the advisory’s stated prerequisite, not a vendor-published workaround.
The two-factor report concerns a different trust boundary. Its web API authentication check examines one path representation while the router accepts another equivalent representation. Someone who already knows the password can reach account-management actions without supplying the second factor; the report says a site administrator account would expose administrator privileges.
The LDAP report describes identity confusion rather than a password bypass for every account. Gogs selects a local LDAP account by email, while the directory authenticates an entry using its configured identifier. If those identities differ but the strings match the reported condition, the authenticated entry can be assigned the other account’s session.
The stored-XSS report depends on a repository setting and a user click. A repository administrator can supply an unsafe external issue-tracker link format, and the newer client inserts rendered commit-subject HTML without the earlier sanitization step. A visitor who clicks the issue reference can run script in the Gogs origin with that visitor’s privileges; the advisory does not claim server-side code execution.
What Should Gogs Owners Check First?
Record the exact deployed tag or development commit, enabled login sources, exposed web interface, repository permissions and protected-branch rules. Compare those facts with the matrix before opening a change ticket. A vulnerability management process should keep each advisory and its evidence as a separate item.
- Confirm the running buildRecord the stable tag or development commit and match only the relevant advisory rows.
- Review protected branchesIdentify Write collaborators who can merge and check recent merges against the intended approval rules.
- Review authenticationInventory two-factor accounts on development builds and LDAP mappings on pre-0.15 builds.
- Review repository settingsIdentify repositories using external issue trackers and who can change their formats.
- Verify a real fixCheck the Gogs release page and relevant advisory again before claiming remediation.
For the two-factor condition, prioritize accounts with administrative rights and passwords exposed through other channels. For LDAP, compare each local account’s intended directory identity with the directory entry used at login. These are defensive review steps drawn from the reports, not claims that any particular deployment has been compromised.
For stored XSS, inventory public repositories with external issue trackers and limit who can edit their settings while awaiting a verified build. Avoid presenting a browser-side filter as a complete product patch. The advisory calls for URL-scheme validation and sanitization at the API boundary.
What Does the Gogs Discussion Count Mean?
Brandefense Blackhole counted 213 dark-chat posts mentioning Gogs from August 21 through November 19, 2026. The measured unit is posts matching the product name across that period, not unique actors, vulnerable installations or incidents. This broad discussion count cannot establish exploitation of any of these four advisories.
For comparison, our earlier Gitea security-fix analysis also separates exposure conditions from a blanket “upgrade now” claim. Apply the same discipline here: record which branch is installed, which feature is enabled, and which build can actually be obtained. Then recheck the vendor records as fix and release information changes.
Frequently Asked Questions
Does upgrading to Gogs 0.14.4 fix all four advisories?
No. The protected-branch and LDAP advisories include versions before 0.15.0, while the other two describe 0.15.0+dev builds.
Is there a published fix for the protected-branch bypass?
The advisory lists “None” under patched versions. Check the vendor record and release notes before claiming a fix is available.
Do the two-factor and stored-XSS reports affect all stable Gogs builds?
Their affected-version fields name 0.15.0+dev. The reports do not establish that every stable 0.14 build has those two flaws.
