When a push was authenticated with a deploy key, Gitea recorded the repository owner as the pusher, so permission checks in the push hook pipeline evaluated the owner instead of the deploy key. A holder of a writable deploy key could create protected tags without being on the tag allow list and change repository visibility through push options, for example making a private repository public. Pull requests created through the AGit flow with a deploy key were also attributed to the owner.
CVE-2026-79960
HIGHPre-NVD 7.17.1Trending — 4 sources updated this week
EchelonGraph scoreLOW confidence
This high-severity CVE scores 7.1 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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).
Triggered by: NVD CVSS baseline
Sources: cisa-adp
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.1Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 7.1
- EG Score
- 7.1HIGHlow confidence
- EG Risk
- 32EG Risk 32/100CISA SSVC
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 computedSeverity71% × 45%Exploitation0% × 40%Automatability0% × 15%CISA SSVC: Track at every mission impact level.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.1%
- EPSS %ILE
- 3rd
- KEV
- Not listed
CISA SSVCTrack at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
October 6, 2026
Last Modified
October 7, 2026
Advisory Details (4)
Auto-updated Oct 7, 2026Patch available. Sources: github_release, github, github_pr.
github_release Patch Available
v28.0.0
Patch available: go-gitea/gitea v28.0.0
https://github.com/go-gitea/gitea/releases/tag/v28.0.0github_pr
feat: add deploy tokens
Fix merged in go-gitea/gitea PR #37306 on 2026-08-26 — awaiting tagged release
https://github.com/go-gitea/gitea/pull/37306githubMentions a patch (unverified)
Deploy keys impersonate the repository owner in the hook pipeline · Advisory · go-gitea/gitea · GitHub
https://github.com/go-gitea/gitea/security/advisories/GHSA-7769-9pr9-m24hWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× 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-10-07 23:48 UTCEPSS rescore
- 2026-10-07 14:27 UTCEG score recompute▲ 7.10
- 2026-10-07 14:26 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
- 2026-10-06 20:31 UTCNVD update
- 2026-10-06 19:32 UTCEG score recompute
- 2026-10-06 19:31 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-79960?
CVE-2026-79960 is a high vulnerability published on October 6, 2026. When a push was authenticated with a deploy key, Gitea recorded the repository owner as the pusher, so permission checks in the push hook pipeline evaluated the owner instead of the deploy key. A holder of a writable deploy key could create protected tags without being on the tag allow list and…
When was CVE-2026-79960 disclosed?
CVE-2026-79960 was first published on October 6, 2026, with the most recent update on October 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-79960 actively exploited?
CVE-2026-79960 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-79960?
CVE-2026-79960 has a CVSS v3.1 base score of 7.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-79960?
A fix for CVE-2026-79960 is available: update to the fixed version the vendor names in its advisory.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-79960
Is Your Infrastructure Affected by CVE-2026-79960?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.