CVE-2026-25119 is a high-severity security vulnerability in gogs.io/gogs (go), affecting versions <= 0.14.2. It is fixed in 0.14.3.
Summary When ENABLEREVERSEPROXYAUTHENTICATION is enabled, Gogs accepts the configured authentication header (default: X-WEBAUTH-USER) directly from client requests without validating that the request originated from a trusted reverse proxy. Any remote attacker who can reach the Gogs service can forge this header to impersonate any user or trigger automatic account creation, completely bypassing authentication. Root Cause The vulnerability exists because Gogs reads the authentication header directly from the incoming HTTP request without any verification that the header was set by a trusted reverse proxy. Vulnerable Code Flow In internal/context/auth.go lines 206-234: The code has zero validation that: The request came through a reverse proxy The header was set by the proxy (not the client) Gogs is actually behind a reverse proxy The direct access to Gogs is restricted The vulnerability occurs when: Gogs is publicly accessible (e.g., 0.0.0.0:3000) ENABLEREVERSEPROXYAUTHENTICATION = true Proof of Concept Prerequisites Gogs instance with the following configuration in custom/conf/app.ini: An attacker can impersonate any user including administrators: <img width="1835" height="1143" alt="impersonationexample" src="https://github.com/user-attachments/assets/bae60772-5eb3-4f54-9fe0-5db01595bd56" /> Recommended Fixes Add validation to ensure headers come from trusted sources: Add configuration option: References CWE-290: Authentication Bypass by Spoofing OWASP: Authentication Cheat Sheet OWASP Top 10 2021 - A07: Identification and Authentication Failures
go
gogs.io/gogs (<= 0.14.2)gogs.io/gogs → 0.14.3 (go)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-25119 is reachable in your applications. Explore open-source security for your team.
See if CVE-2026-25119 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2026-25119 in your environment →Upgrade gogs.io/gogs to 0.14.3 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2026-25119 is a high-severity security vulnerability in gogs.io/gogs (go), affecting versions <= 0.14.2. It is fixed in 0.14.3.
gogs.io/gogs (go) versions <= 0.14.2 is affected.
Yes. CVE-2026-25119 is fixed in 0.14.3. Upgrade to this version or later.
Whether CVE-2026-25119 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.
Upgrade gogs.io/gogs to 0.14.3 or later.