CVE-2026-26276 is a high-severity cross-site scripting (XSS) vulnerability in gogs.io/gogs (go), affecting versions <= 0.13.3. No fixed version is listed yet.
Summary It was confirmed in a test environment that an attacker can store an HTML/JavaScript payload in a repository’s Milestone name, and when another user selects that Milestone on the New Issue page (/issues/new), a DOM-Based XSS is triggered. Impact Theft of information accessible in the victim’s session. Extraction of CSRF tokens and submission of state-changing requests with the victim’s privileges. Repository operations performed with the victim’s privileges (Issue operations, settings changes, etc.). (The impact scope depends on the victim’s permission level.) Remediation A fix is available at https://github.com/gogs/gogs/releases/tag/v0.14.2
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.
CVE-2026-26276 has a CVSS score of 7.3 (High). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.
go
gogs.io/gogs (<= 0.13.3)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-26276 is reachable in your applications. Explore open-source security for your team.
See if CVE-2026-26276 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2026-26276 in your environment →No fixed version is listed for CVE-2026-26276 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.
CVE-2026-26276 is a high-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.
CVE-2026-26276 has a CVSS score of 7.3 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
gogs.io/gogs (go) versions <= 0.13.3 is affected.
No fixed version is listed for CVE-2026-26276 yet. Monitor the advisory for updates and apply mitigations in the interim.
Whether CVE-2026-26276 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
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.
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.