gogs.io/gogs

CVE-2026-26195

CVE-2026-26195 is a medium-severity cross-site scripting (XSS) vulnerability in gogs.io/gogs (go), affecting versions <= 0.13.3. No fixed version is listed yet.

Key facts
CVSS score
N/A
Medium
Attack vector
Not available
Issuing authority
GitHub Advisory Database
Affected package
gogs.io/gogs
Fixed in
Not available
Disclosed
2026

Summary

Summary Stored XSS is still possible through unsafe template rendering that mixes user input with safe() plus permissive sanitizer handling of data URLs. Details safe() still turns off escaping: internal/template/template.go func safe(raw string) template.HTML { return template.HTML(raw) } Branch pages still render committer names using safe(): templates/repo/branches/overview.tmpl templates/repo/branches/all.tmpl templates/repo/wiki/view.tmpl The locale still injects a raw second argument: conf/locale/localeen-US.ini (branches.updatedby = updated %[1]s by %[2]s) Impact An attacker who can inject commit metadata such as author/committer name can trigger script execution on affected pages, leading to session abuse, CSRF token theft, or unauthorized actions. Recommended Fix Untrusted arguments should be escaped before being used in translations. Data URLs should be limited or blocked in the sanitizer. Remediation A fix is available at https://github.com/gogs/gogs/releases/tag/v0.14.2.

Impact

What is cross-site scripting (XSS)?

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

Affected versions

go

  • gogs.io/gogs (<= 0.13.3)

Security releases

Not available
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether CVE-2026-26195 is reachable in your applications. Explore open-source security for your team.

See if CVE-2026-26195 is reachable in your applications. Get a demo

Already deployed Kodem? See CVE-2026-26195 in your environment

Remediation advice

No fixed version is listed for CVE-2026-26195 yet.

In the interim: Validate and encode untrusted input before rendering it as HTML. Applying a Content Security Policy reduces the impact if encoding is bypassed.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2026-26195

What is CVE-2026-26195?

CVE-2026-26195 is a medium-severity cross-site scripting (XSS) vulnerability in gogs.io/gogs (go), affecting versions <= 0.13.3. No fixed version is listed yet. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

Which versions of gogs.io/gogs are affected by CVE-2026-26195?

gogs.io/gogs (go) versions <= 0.13.3 is affected.

Is there a fix for CVE-2026-26195?

No fixed version is listed for CVE-2026-26195 yet. Monitor the advisory for updates and apply mitigations in the interim.

Is CVE-2026-26195 exploitable, and should I be worried?

Whether CVE-2026-26195 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether CVE-2026-26195 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-26195?

No fixed version is listed yet. In the interim: Validate and encode untrusted input before rendering it as HTML. Applying a Content Security Policy reduces the impact if encoding is bypassed.

Stop the waste.
Protect your environment with Kodem.