Gogs is an open source self-hosted Git service. Prior to 0.14.3, 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 vulnerability is fixed in 0.14.3.
CVE-2026-47267
This high-severity CVE scores 8.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 68% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.3
- EG Score
- 8.3(medium)
- EPSS
- 32.7%
- KEV
- Not listed
Published
June 22, 2026
Last Modified
June 25, 2026
Advisory Details (3)
Auto-updated Jun 24, 2026SSRF in webhook deliveries · Advisory · gogs/gogs · GitHub
https://github.com/gogs/gogs/security/advisories/GHSA-c4v7-xg93-qf8gsecurity: don't follow redirects on webhook delivery
Fix merged in gogs/gogs PR #8263 on 2026-05-19 — awaiting tagged release
https://github.com/gogs/gogs/pull/8263commit 199cf4fd5bbe (gogs/gogs)
Fix landed in gogs/gogs commit 199cf4fd5bbe — awaiting tagged release
https://github.com/gogs/gogs/commit/199cf4fd5bbe40b92f6dc8d649e241fd7a8d0018Vendor Advisories for CVE-2026-47267(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| gogs.io/gogs | — | 0.14.3 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 32× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-28 14:07 UTCEPSS rescore
Show 7 moreShow fewer
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 00:05 UTCEG score recompute▲ 8.30
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-24 22:03 UTCNVD updateCVSS v3 → 8.3 · severity → HIGH
- 2026-06-22 23:31 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-47267?
When was CVE-2026-47267 disclosed?
Is CVE-2026-47267 actively exploited?
What is the CVSS score of CVE-2026-47267?
How do I remediate CVE-2026-47267?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47267
Is Your Infrastructure Affected by CVE-2026-47267?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.