Gogs has SSRF in webhook deliveries

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L

EPSS

• CVE-2026-47267: 0.42% estimated exploitation activity in the next 30 days; percentile 36.34 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The fix for CVE-2022-1285 prevents adding webooks or running webhooks with URLs with a hostname that resolves in localCIDRs. However, webhooks still follow redirects allowing to access hostname inside localCIDRs. This was already communicated in the initial report but it looks like there was a bit of a miscommunication. Details By creating a webook pointing to any URL that will return the following: It is possible to access 169.254.169.254 PoC 1. Run netcat on any server 2. Use this server as the webhook URL 3. Once you get the request from the webhook (for example by testing it), copy the response above Results from running this on try.gogs: Impact Server Side Request Forgery Fix The "simplest way" to fix it is most likely to leverage Client.CheckRedirect https://pkg.go.dev/net/http#hdr-ClientsandTransports to check if the redirect is pointing to a blocked hostname

Published by the source

22 Jun 2026, 22:44 UTC

Last modified by the source

21 Jul 2026, 13:16 UTC

Source last checked

26 Oct 2026, 15:27 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-c4v7-xg93-qf8g

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-47267

Advisory: Gogs has SSRF in webhook deliveries
IDs: CVE-2026-47267, GHSA-c4v7-xg93-qf8g
Record: https://patchnext.com/advisories/cve-2026-47267 (revision 1, source checked 26 Oct 2026, 15:27 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: gogs.io/gogs 0.14.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go gogs.io/gogs: affected <= 0.14.2; fixed in 0.14.3

## Suggested inspection (read-only)
- Go gogs.io/gogs: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on gogs.io/gogs.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-c4v7-xg93-qf8g (GitHub-reviewed advisory GHSA-c4v7-xg93-qf8g lists affected ranges: Go gogs.io/gogs >=0 <=0.14.2)

Commands are suggestions: review each one before running it.