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

Back
New CVE Detected

CVE-2026-47267 – SSRF via Webhook Redirect 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-47267 is a high-severity Server-Side Request Forgery (SSRF) vulnerability in Gogs, the open-source self-hosted Git service, affecting all versions prior to 0.14.3. The flaw is an incomplete fix bypass: while the earlier patch for CVE-2022-1285 blocked webhook requests to URLs whose hostnames resolve directly to local network ranges (localCIDRs), Gogs still follows HTTP redirects during webhook delivery, allowing an attacker to pivot through a redirect to reach internal or private network resources. The CVSS v3.1 base score is 8.3 (HIGH) with no authentication or user interaction required.

Technical details

  • Root cause: The SSRF filter introduced in the CVE-2022-1285 fix validates the initial webhook destination URL against localCIDRs, but does not prevent the HTTP client from following 3xx redirects to a second URL that resolves to a private address. This is a classic SSRF-via-open-redirect bypass pattern.
  • Trigger conditions: An actor configures or triggers a webhook whose destination is an attacker-controlled server. That server responds with an HTTP redirect (e.g., 301 Moved Permanently) pointing to an internal resource such as http://169.254.169.254/latest/meta-data/ (cloud instance metadata) or any other host within a local CIDR range.
  • Attack vector: Network-reachable; no authentication required (PR:N); no user interaction required (UI:N). The changed scope (S:C) indicates the impact extends beyond the vulnerable Gogs component to internal systems that should not be network-accessible from the internet.
  • Impact: Partial confidentiality loss (exposure of internal service responses, cloud metadata, credentials), partial integrity impact (ability to interact with internal HTTP endpoints), and partial availability impact — all against resources inside the private network perimeter.
  • CWE: CWE-918 (Server-Side Request Forgery)

Affected software

  • Gogs all versions prior to 0.14.3

Severity

  • CVSS v3.1 Base Score: 8.3 (HIGH)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L

Mitigation and recommended actions

  • Immediate – Patch: Upgrade Gogs to version 0.14.3 or later, which contains the official fix. The patch is tracked in the GitHub repository under pull request #8263 (commit 199cf4fd).
  • If patching is not immediately possible: Restrict network access to the Gogs instance so that only trusted users can configure or trigger webhooks. At the infrastructure level, enforce egress filtering on the host running Gogs to block outbound connections to RFC-1918 addresses (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), link-local addresses (169.254.0.0/16), and loopback (127.0.0.0/8). This does not eliminate the vulnerability but significantly reduces exploitability.
  • Audit existing webhook configurations for any entries pointing to external redirect services or suspicious third-party URLs.

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