Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-25119 – Authentication Bypass – Gogs prior to 0.14.3

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-25119 is a high-severity authentication bypass vulnerability (CWE-290) in Gogs, an open-source self-hosted Git service, affecting all versions prior to 0.14.3. When the reverse proxy authentication feature is enabled, Gogs accepts the X-WEBAUTH-USER header directly from any incoming client request without verifying that it originated from a trusted reverse proxy, allowing a remote, unauthenticated attacker to completely bypass authentication. The vulnerability is fixed in Gogs 0.14.3.

Technical details

  • Root cause: The authentication logic in internal/context/auth.go reads the configured reverse proxy authentication header (default: X-WEBAUTH-USER) directly from incoming HTTP requests without performing any validation that the request actually originated from a trusted proxy. There is zero verification of the request source before the header value is honoured as an authenticated identity.
  • Trigger conditions: Exploitation requires the ENABLE_REVERSE_PROXY_AUTHENTICATION = true setting to be active in the Gogs configuration, and network access to the Gogs service.
  • Attack vector: A remote, unauthenticated attacker sends an HTTP request to the Gogs service with a forged X-WEBAUTH-USER header set to any target username. No credentials, tokens, or prior access are required.
  • Impact: Complete authentication bypass — the attacker can impersonate any existing user (including administrators) or trigger automatic creation of new accounts, gaining full access to repositories and administrative functionality controlled by the impersonated account.

Affected software

  • Gogs all versions prior to 0.14.3 (i.e., ≤ 0.14.2) when ENABLE_REVERSE_PROXY_AUTHENTICATION is enabled

Severity

CVSS v3.1 base score: 7.5 (High)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Mitigation and recommended actions

  • Immediate: Upgrade to Gogs 0.14.3 or later. This release restricts acceptance of the reverse proxy authentication header to requests originating from configured trusted proxy IP addresses only.
  • If immediate patching is not feasible: Disable ENABLE_REVERSE_PROXY_AUTHENTICATION in the Gogs configuration, or enforce network-level controls that ensure only the trusted reverse proxy can reach the Gogs service port directly — preventing attackers from sending forged headers.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge