Cyber Resilience

CVE-2026-26276

XSS in Gogs ≤ 0.14.2

XSS
Published
05 March 2026
Modified
05 March 2026
Patch / advisory
View advisory
CVSS Score v3.1 7.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N
EPSS Score 0.0018 8th percentile
Risk Priority 52 floored blend · peak EPSS

Summary

CVE-2026-26276 is a high-severity Cross-site Scripting (CWE-79) vulnerability in Gogs Gogs. Its CVSS base score is 7.3 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Browser Session Hijacking (T1185); ranked at the 8th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-26276 is a DOM-based cross-site scripting (XSS) vulnerability, classified under CWE-79, affecting Gogs, an open source self-hosted Git service. In versions prior to 0.14.2, the flaw allows an attacker to store an HTML/JavaScript payload in a repository's Milestone name. This payload is then triggered as a DOM-based XSS when another user selects that Milestone on the New Issue page (/issues/new). The vulnerability carries a CVSS v3.1 base score of 7.3 (AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N), indicating high confidentiality and integrity impacts with no availability disruption.

An attacker requires low privileges, such as repository write access to create or modify a Milestone with a malicious payload. Exploitation occurs over the network with low complexity but demands user interaction, specifically a victim navigating to the New Issue page and selecting the tainted Milestone. Successful exploitation enables the payload to execute in the victim's browser context, potentially leading to session hijacking, data theft, or further phishing attacks against the targeted user.

The issue has been addressed in Gogs version 0.14.2, as detailed in the official release notes, a corresponding pull request, and the project's security advisory. Security practitioners should upgrade to version 0.14.2 or later to mitigate the vulnerability, with no additional workarounds specified in the provided references.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

Gogs is an open source self-hosted Git service. Prior to version 0.14.2, 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…

more

is triggered. This issue has been patched in version 0.14.2.

CWE(s)
CWE-79

Related Threats

MITRE ATT&CK Enterprise Techniques

T1185 Browser Session Hijacking Collection
Adversaries may take advantage of security vulnerabilities and inherent functionality in browser software to change content, modify user-behaviors, and intercept information as part of various browser session hijacking techniques.
attack.mitre.org →
T1539 Steal Web Session Cookie Credential Access
An adversary may steal web application or service session cookies and use them to gain access to web applications or Internet services as an authenticated user without needing credentials.
attack.mitre.org →
T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
attack.mitre.org →
T1189 Drive-by Compromise Initial Access
Adversaries may gain access to a system through a user visiting a website over the normal course of browsing.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2022-32174Same product: Gogs Gogs
CVE-2023-25837Shared CWE-79
CVE-2023-22438Shared CWE-79
CVE-2023-27614Shared CWE-79
CVE-2023-47164Shared CWE-79
CVE-2023-49145Shared CWE-79
CVE-2023-47853Shared CWE-79
CVE-2023-28474Shared CWE-79
CVE-2023-37636Shared CWE-79
CVE-2023-1006Shared CWE-79

Affected Assets

gogs
gogs
≤ 0.14.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.1.2
  • V1.3.2

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover missing or incorrect input neutralization through targeted web-application tests.

SI-10 Information Input Validation good match

Input validation directly enforces neutralization of untrusted data before it reaches web output generation.

SI-15 Information Output Filtering good match

Output filtering can catch or sanitize unneutralized script content before it is served to users.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly target introduction of XSS via coding standards/testing (mostly), yet the single broad outcome leaves many specific neutralization vectors unaddressed (partial).

PR.PS-02 partial match
prevents

Patching and EOL replacement can remediate known XSS instances in libraries or frameworks (partial) but do nothing to enforce input neutralization in application code (none).

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Secure-coding testing and automated code-analysis tools are applied to detect improper neutralization of script-related content during web-page generation.

A.5.6 Contact with special interest groups partial match
prevents

Knowledge exchange on emerging attack techniques and patches reduces the likelihood that cross-site scripting flaws remain unaddressed in deployed applications.

A.5.7 Threat intelligence partial match
prevents

Operational indicators of compromise for web-application attacks can be incorporated into WAF or input-filtering rules, lowering the likelihood that unsanitized data reaches the browser.

A.8.25 Secure development life cycle partial match
prevents

Requiring language-specific secure-coding standards and automated scanning during the SDLC catches missing output encoding or improper neutralization of untrusted data before the software reaches production.

A.8.28 Secure coding partial match
prevents

Secure-coding standards, SAST scans and removal of insecure code samples together eliminate the failure to neutralize script content that produces cross-site scripting flaws.

A.8.7 Protection against malware none match
none

Webpage malware scanning and block-listing of known malicious sites reduce the likelihood that reflected or stored script payloads reach a user’s browser.

References