CVE-2026-34966

HIGHPre-NVD 7.67.6—
EchelonGraph scoreHIGH confidence

Score 7.6 from GitHub Security Advisory (severity: HIGH) published 2026-08-05. the CNA's CVSS baseline 7.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, epss, ghsa
Trending — 3 sources updated this weekElevated
7.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.6Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Gitea prior to 1.27.0 contains a server-side request forgery vulnerability that allows authenticated attackers to bypass SSRF protections by exploiting HTTP fetch operations in migration and OAuth avatar code paths that use Go's default http.Get without a custom DialContext. Attackers can supply arbitrary URLs through release asset download URLs, pull-request patch URLs, or OAuth avatar endpoints to reach internal services, cloud instance-metadata endpoints, or read local files such as the application configuration containing database credentials and signing secrets, with exfiltrated content persisted as migration release assets for later retrieval.

CVSS v3
7.6
EG Score
7.6(high)
EG Risk
50(Track)
EG Risk 50/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity76% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
24%
KEV
Not listed

Published

August 5, 2026

Last Modified

August 14, 2026

Advisory Details (4)

Auto-updated Aug 5, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
generic

Gitea prior to 1.27.0 SSRF via Migration URI Fetch Bypass | Advisories | VulnCheck

https://www.vulncheck.com/advisories/gitea-prior-to-ssrf-via-migration-uri-fetch-bypass
github_commit

commit b969123b7fac (go-gitea/gitea)

Fix landed in go-gitea/gitea commit b969123b7fac — awaiting tagged release

https://github.com/go-gitea/gitea/commit/b969123b7fac51c88daab5cb64e5b2f4abd53288
github Patch Available🟡 PoC Available

SSRF via Migration Asset Downloads Bypasses hostmatcher — Reads Internal Files and Cloud Metadata · Advisory · go-gitea/gitea · GitHub

https://github.com/go-gitea/gitea/security/advisories/GHSA-2wm4-vwp6-v7xc
generic

GitHub - go-gitea/gitea: Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD · GitHub

https://github.com/go-gitea/gitea

Vendor Advisories for CVE-2026-34966(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 1 ecosystem)
Go(2)
PackageVulnerable rangeFixed inDependents
code.gitea.io/gitea—1.27.0—
gitea.dev—1.27.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 29× in last 7d / 64× 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.

  1. 2026-08-20 14:55 UTCGHSA enrichment
  2. 2026-08-20 03:05 UTCEG score recompute
  3. 2026-08-20 03:05 UTCGHSA enrichment
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-19 15:21 UTCGHSA enrichment
  6. 2026-08-19 03:30 UTCGHSA enrichment
  7. 2026-08-18 15:44 UTCEG score recompute
  8. 2026-08-18 15:44 UTCGHSA enrichment
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-18 03:30 UTCGHSA enrichment
  11. 2026-08-17 15:36 UTCEG score recompute
  12. 2026-08-17 15:36 UTCGHSA enrichment
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-17 03:52 UTCGHSA enrichment
  15. 2026-08-16 16:07 UTCEG score recompute
  16. 2026-08-16 16:07 UTCGHSA enrichment
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 04:23 UTCEG score recompute
  19. 2026-08-16 04:23 UTCGHSA enrichment
  20. 2026-08-16 02:14 UTCEPSS rescore
  21. 2026-08-15 16:39 UTCGHSA enrichment
  22. 2026-08-15 04:55 UTCEG score recompute
  23. 2026-08-15 04:55 UTCGHSA enrichment
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-14 17:11 UTCEG score recompute
Show 39 more
  1. 2026-08-14 17:11 UTCGHSA enrichment
  2. 2026-08-14 12:21 UTCGHSA enrichment
  3. 2026-08-14 00:37 UTCEG score recompute
  4. 2026-08-14 00:37 UTCGHSA enrichment
  5. 2026-08-13 22:00 UTCEPSS rescore
  6. 2026-08-13 12:52 UTCGHSA enrichment
  7. 2026-08-13 01:08 UTCEG score recompute
  8. 2026-08-13 01:08 UTCGHSA enrichment
  9. 2026-08-12 13:50 UTCEPSS rescore
  10. 2026-08-12 13:24 UTCGHSA enrichment
  11. 2026-08-12 01:40 UTCGHSA enrichment
  12. 2026-08-11 13:56 UTCEG score recompute
  13. 2026-08-11 13:56 UTCGHSA enrichment
  14. 2026-08-11 02:12 UTCEG score recompute
  15. 2026-08-11 02:12 UTCGHSA enrichment
  16. 2026-08-11 00:00 UTCEPSS rescore
  17. 2026-08-10 14:28 UTCGHSA enrichment
  18. 2026-08-10 02:44 UTCGHSA enrichment
  19. 2026-08-09 15:00 UTCEG score recompute
  20. 2026-08-09 15:00 UTCGHSA enrichment
  21. 2026-08-09 13:46 UTCEPSS rescore
  22. 2026-08-09 03:16 UTCEG score recompute
  23. 2026-08-09 03:16 UTCGHSA enrichment
  24. 2026-08-08 16:37 UTCEPSS rescore
  25. 2026-08-08 15:32 UTCGHSA enrichment
  26. 2026-08-08 03:47 UTCEG score recompute
  27. 2026-08-08 03:47 UTCGHSA enrichment
  28. 2026-08-07 16:03 UTCGHSA enrichment
  29. 2026-08-07 04:19 UTCGHSA enrichment
  30. 2026-08-06 16:34 UTCEG score recompute
  31. 2026-08-06 16:34 UTCGHSA enrichment
  32. 2026-08-06 15:33 UTCEG score recompute
  33. 2026-08-06 15:33 UTCGHSA enrichment
  34. 2026-08-06 13:46 UTCEPSS rescore
  35. 2026-08-06 09:01 UTCEG score recompute
  36. 2026-08-06 09:01 UTCGHSA enrichment
  37. 2026-08-05 21:17 UTCEG score recompute
  38. 2026-08-05 20:45 UTCEG score recompute
  39. 2026-08-05 20:45 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-34966?
CVE-2026-34966 is a high vulnerability published on August 5, 2026. Gitea prior to 1.27.0 contains a server-side request forgery vulnerability that allows authenticated attackers to bypass SSRF protections by exploiting HTTP fetch operations in migration and OAuth avatar code paths that use Go's default http.Get without a custom DialContext. Attackers can supply…
When was CVE-2026-34966 disclosed?
CVE-2026-34966 was first published in the National Vulnerability Database on August 5, 2026, with the most recent update on August 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-34966 actively exploited?
CVE-2026-34966 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 75.8% of all scored CVEs.
What is the CVSS score of CVE-2026-34966?
CVE-2026-34966 has a CVSS v4.0 base score of 7.6 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-34966?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-34966, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-34966

Explore →

Is Your Infrastructure Affected by CVE-2026-34966?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs